Topic: POOL OPERATORS! A request... (Read 1576 times)
Good to see my pro-active attempt gained some interest (Sorry if it was spammy!) 
OK, how about something like this:
(We'll leave workers and previous blocks for later versions.)
block =
{
"duration" =,
"shares_total" =,
"shares_submitted" =,
"reward" =
}
user =
{
"API" = 1.0.0
"current_round" = {},
"hash_rate" =,
"last_activity" =,
"confirmed_reward" ==120 valid blocks) in Satoshis>,
"unconfirmed_reward" =,
"total_payout" =,
"last_payout_value" =,
"last_payout_time" =
OK, how about something like this:
(We'll leave workers and previous blocks for later versions.)
block =
{
"duration" =
"shares_total" =
"shares_submitted" =
"reward" =
}
user =
{
"API" = 1.0.0
"current_round" = {
"hash_rate" =
"last_activity" =
"confirmed_reward" =
"unconfirmed_reward" =
"total_payout" =
"last_payout_value" =
"last_payout_time" =
I'd be interested in supporting this.
How similar are the APIs of Deepbit and Slush? Perhaps a standard can be based off of those.
How similar are the APIs of Deepbit and Slush? Perhaps a standard can be based off of those.
Watching.
I would be nice, but it is somewhat irrelevant
But if someone wants to write up a standard MtRed would support it.
I would be nice, but it is somewhat irrelevant
But if someone wants to write up a standard MtRed would support it.
AFAIR, slush was the first one to implement JSON API, so I just used same keys when possible in my version of API.
That's why it says "confirmed_reward" instead of just "balance".
That's why it says "confirmed_reward" instead of just "balance".
I'll +1 this. I'm all about the infoporn and the sooner someone writes a standard for APIs the sooner I get my better quality infoporn.
If someone wants to implement it for Eligius, feel free to email me for webserver access...
I'd be happy to implement something if it were agreed upon.
p2pool is open source so you can do it yourself.
Also there would then be a reference implementation for others to copy..
Also there would then be a reference implementation for others to copy..
No desire to do this at all from anyone?
My suggested info:
API version
Current round duration
Current round shares total
Current round shares submitted
Current round estimated reward BTC
Current hash rate
Last activity
Confirmed BTC
Unconfirmed BTC
Total payout BTC
Last payout BTC
Last payout time
Payout threshold
My suggested info:
API version
Current round duration
Current round shares total
Current round shares submitted
Current round estimated reward BTC
Current hash rate
Last activity
Confirmed BTC
Unconfirmed BTC
Total payout BTC
Last payout BTC
Last payout time
Payout threshold
I'll expand a little...
Provide a standard output with basic info about the user/worker, MAYBE pool as well.
You can decide among yourselves what this 'basic info' is.
This isn't to replace your current APIs but to add something standard that apps can receive and not have to worry about writing X number of decoders.
Thanks
Provide a standard output with basic info about the user/worker, MAYBE pool as well.
You can decide among yourselves what this 'basic info' is.
This isn't to replace your current APIs but to add something standard that apps can receive and not have to worry about writing X number of decoders.
Thanks
Could you, between yourselves, sort out a standard JSON API interface.
K, thanks.
K, thanks.
Jump to: