[ANN][The Original Multipool - Scrypt/SHA256/Scrypt-N/X11] multipool.us

[Balthazar]

Last 30 Blocks Found - NVC
Block   Confirms   Finder   Time
27,351   12   mike270   2013-06-19 13:04:13

Congratulations

[kslavik]

.....Also I wondered if it was better to order the List having the worker names as keys then have the coins as values to workers? e.g
{"workers":{"name:"{"coin":{"key":"value"},"coin":{"key":"value"}}}}

Reversing Workers tables to Worker->Currency->Key:value,Key:Value, (from "Currency->worker->key:value,key:value) would work as well, with a difference that results will be grouped by workers first.

I think it is better to leave it as it is because sortable workers list per currency would make more sense than
sortable currencies list per worker. I know that we have only hashrate for each worker over there right now as a key:value, but once more values are added (# of shares, difficulty, etc) into the table per worker, sorting would only make sense within a currency.

If anyone interested, my Web-based API reader is right here http://json.karasoft.com with Multipool templates added:

[acc85]

.....Also I wondered if it was better to order the List having the worker names as keys then have the coins as values to workers? e.g
{"workers":{"name:"{"coin":{"key":"value"},"coin":{"key":"value"}}}}

Reversing Workers tables to Worker->Currency->Key:value,Key:Value, (from "Currency->worker->key:value,key:value) would work as well, with a difference that results will be grouped by workers first.

I think it is better to leave it as it is because sortable workers list per currency would make more sense than
sortable currencies list per worker. I know that we have only hashrate for each worker over there right now as a key:value, but once more values are added (# of shares, difficulty, etc) into the table per worker, sorting would only make sense within a currency.

If anyone interested, my Web-based API reader is right here http://json.karasoft.com with Multipool templates added:

hmm I noticed that in trc coin list of workers, there are more workers than there are in the other coins, I'm guessing those were deleted workers also included in the list?

Also just suggested the Worker->Currency->Key:value,Key:Value, cause in most miner monitors i've seen.. it's more of a case os seeing which worker is active than seeing what coin is being minerd by what miner, afterall. it is a worker list

[kslavik]

.....Also I wondered if it was better to order the List having the worker names as keys then have the coins as values to workers? e.g
{"workers":{"name:"{"coin":{"key":"value"},"coin":{"key":"value"}}}}

Reversing Workers tables to Worker->Currency->Key:value,Key:Value, (from "Currency->worker->key:value,key:value) would work as well, with a difference that results will be grouped by workers first.

I think it is better to leave it as it is because sortable workers list per currency would make more sense than
sortable currencies list per worker. I know that we have only hashrate for each worker over there right now as a key:value, but once more values are added (# of shares, difficulty, etc) into the table per worker, sorting would only make sense within a currency.

If anyone interested, my Web-based API reader is right here http://json.karasoft.com with Multipool templates added:

hmm I noticed that in trc coin list of workers, there are more workers than there are in the other coins, I'm guessing those were deleted workers also included in the list?

Also just suggested the Worker->Currency->Key:value,Key:Value, cause in most miner monitors i've seen.. it's more of a case os seeing which worker is active than seeing what coin is being minerd by what miner, afterall. it is a worker list

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.
 
If only value inside the table would be "hash rate" per Currency/per worker, then table would look great if workers would be on Y axis and currencies on the X (I agree with you there):

Code:

              LTC   FTC     DGC    NVC    MNC
Worker 1       0     0       0      0     85.3
Worker 2       0     0       0      0     300.5

it would look like that internally:

Code:

{"worker1":{"coin 1":"hashrate","coin 2":"hashrate"}},
{"worker2":{"coin 1":"hashrate","coin 2":"hashrate"}}

On the other hand if there is more than 1 key:value pairs per worker/per currency, I would still like to see workers in the list (I know it will be several lists: one per currency), which would mean that Currencies should be first grouping parameter.

Multipool specific API reader would display values as they would think is the best (so either way would work), but I have a generic one (I display data as given to me by API), which makes me prefer Currency->Worker->key:value,key:value way.

[acc85]

.....Also I wondered if it was better to order the List having the worker names as keys then have the coins as values to workers? e.g
{"workers":{"name:"{"coin":{"key":"value"},"coin":{"key":"value"}}}}

Reversing Workers tables to Worker->Currency->Key:value,Key:Value, (from "Currency->worker->key:value,key:value) would work as well, with a difference that results will be grouped by workers first.

I think it is better to leave it as it is because sortable workers list per currency would make more sense than
sortable currencies list per worker. I know that we have only hashrate for each worker over there right now as a key:value, but once more values are added (# of shares, difficulty, etc) into the table per worker, sorting would only make sense within a currency.

If anyone interested, my Web-based API reader is right here http://json.karasoft.com with Multipool templates added:

hmm I noticed that in trc coin list of workers, there are more workers than there are in the other coins, I'm guessing those were deleted workers also included in the list?

Also just suggested the Worker->Currency->Key:value,Key:Value, cause in most miner monitors i've seen.. it's more of a case os seeing which worker is active than seeing what coin is being minerd by what miner, afterall. it is a worker list

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.
 
If only value inside the table would be "hash rate" per Currency/per worker, then table would look great if workers would be on Y axis and currencies on the X (I agree with you there):

Code:

              LTC   FTC     DGC    NVC    MNC
Worker 1       0     0       0      0     85.3
Worker 2       0     0       0      0     300.5

it would look like that internally:

Code:

{"worker1":{"coin 1":"hashrate","coin 2":"hashrate"}},
{"worker2":{"coin 1":"hashrate","coin 2":"hashrate"}}

On the other hand if there is more than 1 key:value pairs per worker/per currency, I would still like to see workers in the list (I know it will be several lists: one per currency), which would mean that Currencies should be first grouping parameter.

Multipool specific API reader would display values as they would think is the best (so either way would work), but I have a generic one (I display data as given to me by API), which makes me prefer Currency->Worker->key:value,key:value way.

it wouldn't nessecarily need to look like:

Code:

{"worker1":{"coin 1":"hashrate","coin 2":"hashrate"}},
{"worker2":{"coin 1":"hashrate","coin 2":"hashrate"}}

afterall, it's just a JSON, rearranging the data into presentable data is simple enough, could easily be  {"worker1":{"coin 1":{"hashrate":value, "status":value},"coin 2":{"hashrate":value, "status":value}}}.

it's more aesthetics, not really important, as long as it hold the data it's fine. More importantly is the deleted workers still being retained in teh database or still being parsed to the JSON.

[Zalfrin]

Is the donator list updated manually, just on a slow refresh, or... ? I bumped my donation up to 4% to be a "patron", but I'm not on the list after an hour or so. *shrug*

[flound1129]

I was trying to set donation to a fraction of a percent but the form apparently reset it to 0. Hint Hint.

Try putting in a leading zero (i.e. "0.1" or "0.5") rather than just ".5".. 

[flound1129]

Last 30 Blocks Found - NVC
Block   Confirms   Finder   Time
27,351   12   mike270   2013-06-19 13:04:13

Congratulations

woohoo!

[flound1129]

Is the donator list updated manually, just on a slow refresh, or... ? I bumped my donation up to 4% to be a "patron", but I'm not on the list after an hour or so. *shrug*

Oops!  Bug in the stats..  I had originally planned to set patron at 5% but forgot to modify the SQL when I changed it to 4.  Thanks for reporting, you should be showing up now!

[flound1129]

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.

For some reason the TRC pool worker table was out of sync.  I synced it up with the others.

[acc85]

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.

For some reason the TRC pool worker table was out of sync.  I synced it up with the others.

the api is perfect! .. good job.

Is there any way to get the current pool being mined via scrypt throught he api?

[flound1129]

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.

For some reason the TRC pool worker table was out of sync.  I synced it up with the others.

the api is perfect! .. good job.

Is there any way to get the current pool being mined via scrypt throught he api?

Check out api2.php and let me know what you think.

[acc85]

perfect! gonna start using API key instead

[kslavik]

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.

For some reason the TRC pool worker table was out of sync.  I synced it up with the others.

the api is perfect! .. good job.

Is there any way to get the current pool being mined via scrypt throught he api?

Check out api2.php and let me know what you think.

I would separate Multiport stats to a separate API call: apiMultiport.php (take out worker and pool data). There could be different frequency when those stats are needed, they would be on a different window/screen in the API reader most likely anyway.

[flound1129]

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.

For some reason the TRC pool worker table was out of sync.  I synced it up with the others.

the api is perfect! .. good job.

Is there any way to get the current pool being mined via scrypt throught he api?

Check out api2.php and let me know what you think.

I would separate Multiport stats to a separate API call: apiMultiport.php (take out worker and pool data). There could be different frequency when those stats are needed, they would be on a different window/screen in the API reader most likely anyway.

They're fairly inexpensive operations, and they're cached..  Are they breaking your reader?

[flound1129]

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.

For some reason the TRC pool worker table was out of sync.  I synced it up with the others.

the api is perfect! .. good job.

Is there any way to get the current pool being mined via scrypt throught he api?

Check out api2.php and let me know what you think.

I would separate Multiport stats to a separate API call: apiMultiport.php (take out worker and pool data). There could be different frequency when those stats are needed, they would be on a different window/screen in the API reader most likely anyway.

By the way, the display is different when there's no API key.  It just shows the hashrates for the various currencies.

[kslavik]

There is something wrong with worker deletion: wrong worker is deleted when I tried to delete one, and they are not completely gone from the database.

For some reason the TRC pool worker table was out of sync.  I synced it up with the others.

the api is perfect! .. good job.

Is there any way to get the current pool being mined via scrypt throught he api?

Check out api2.php and let me know what you think.

I would separate Multiport stats to a separate API call: apiMultiport.php (take out worker and pool data). There could be different frequency when those stats are needed, they would be on a different window/screen in the API reader most likely anyway.

They're fairly inexpensive operations, and they're cached..  Are they breaking your reader?

Nothing can break my reader: as long as it has valid JSON, it will display it. 

It is just a matter of preference: only request data which is relevant and needed at the moment. I have seen pools with many different API data sets. My app can display multiple popups directed to different API services, so I would rather have two small windows than one big one with a long scroll bar. Either way is fine in the end, especially of no additional resources is involved in generating those API responses.

What do other people think who are using APIs?

[acc85]

I think it's fine as it is so far .. I've seen worst ..

[nicksmith]

I think it's fine as it is so far .. I've seen worst ..

I would rather make one http call than more, so I like api2.php with it just tagged on the end.

[SullyTex]

Could you please check to see if I am generating anything?  Worker is SullyTex.4

Been hashing for the past hour and even found some blocks but nothing showing on the web page.  I even killed off and created a new worker to verify.

 cgminer version 3.2.0 - Started: [2013-06-19 17:48:30]
---------------------------------------------------------------------------
 (5s):111.8M (avg):211.8Mh/s | A:0  R:6  HW:0  U:0.0/m  WU:3.0/m
 ST: 2  SS: 0  NB: 229  LW: 1278  GF: 3  RF: 0
 Connected to multipool.in diff 32 with stratum as user SullyTex.4
 Block: 16f05bbf79dc9f30...  Diff:3  Started: [19:16:16]  Best share: 193
---------------------------------------------------------------------------
 [P]ool management [G]PU management ettings [D]isplay options [Q]uit
 GPU 0:  65.0C  53%    | 212.9M/212.0Mh/s | A:0 R:6 HW:0 U:0.00/m I:14
---------------------------------------------------------------------------

 [2013-06-19 19:13:21] Stratum from pool 0 detected new block
 [2013-06-19 19:13:32] Found block for pool 0!
 [2013-06-19 19:13:36] Stratum from pool 0 detected new block
 [2013-06-19 19:14:01] Stratum from pool 0 detected new block
 [2013-06-19 19:14:41] Stratum from pool 0 detected new block
 [2013-06-19 19:14:46] Stratum from pool 0 detected new block
 [2013-06-19 19:15:06] Stratum from pool 0 detected new block
 [2013-06-19 19:15:11] Stratum from pool 0 detected new block
 [2013-06-19 19:15:21] Stratum from pool 0 detected new block
 [2013-06-19 19:15:29] Found block for pool 0!
 [2013-06-19 19:15:40] Stratum from pool 0 detected new block
 [2013-06-19 19:15:45] Stratum from pool 0 detected new block
 [2013-06-19 19:16:16] Stratum from pool 0 detected new block