Bitcoin Forum
March 28, 2024, 08:14:31 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: POOL OPERATORS! A request...  (Read 1568 times)
P_Shep (OP)
Legendary
*
Offline Offline

Activity: 1795
Merit: 1198


This is not OK.


View Profile
May 18, 2012, 11:32:29 PM
 #1

Could you, between yourselves, sort out a standard JSON API interface.

K, thanks.
1711656871
Hero Member
*
Offline Offline

Posts: 1711656871

View Profile Personal Message (Offline)

Ignore
1711656871
Reply with quote  #2

1711656871
Report to moderator
According to NIST and ECRYPT II, the cryptographic algorithms used in Bitcoin are expected to be strong until at least 2030. (After that, it will not be too difficult to transition to different algorithms.)
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1711656871
Hero Member
*
Offline Offline

Posts: 1711656871

View Profile Personal Message (Offline)

Ignore
1711656871
Reply with quote  #2

1711656871
Report to moderator
1711656871
Hero Member
*
Offline Offline

Posts: 1711656871

View Profile Personal Message (Offline)

Ignore
1711656871
Reply with quote  #2

1711656871
Report to moderator
P_Shep (OP)
Legendary
*
Offline Offline

Activity: 1795
Merit: 1198


This is not OK.


View Profile
May 18, 2012, 11:40:16 PM
 #2

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 Smiley
P_Shep (OP)
Legendary
*
Offline Offline

Activity: 1795
Merit: 1198


This is not OK.


View Profile
May 21, 2012, 11:45:05 PM
Last edit: May 22, 2012, 05:33:50 PM by P_Shep
 #3

No desire to do this at all from anyone?

 Cry

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
nibor
Sr. Member
****
Offline Offline

Activity: 438
Merit: 291


View Profile
May 22, 2012, 06:24:18 AM
 #4

p2pool is open source so you can do it yourself.
Also there would then be a reference implementation for others to copy..
Inaba
Legendary
*
Offline Offline

Activity: 1260
Merit: 1000



View Profile WWW
May 22, 2012, 01:52:07 PM
 #5

I'd be happy to implement something if it were agreed upon.


If you're searching these lines for a point, you've probably missed it.  There was never anything there in the first place.
Luke-Jr
Legendary
*
Offline Offline

Activity: 2576
Merit: 1186



View Profile
May 22, 2012, 06:17:48 PM
 #6

If someone wants to implement it for Eligius, feel free to email me for webserver access...

enmaku
Hero Member
*****
Offline Offline

Activity: 742
Merit: 500


View Profile
May 22, 2012, 06:23:04 PM
 #7

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.  Grin
[Tycho]
Hero Member
*****
Offline Offline

Activity: 742
Merit: 500



View Profile WWW
May 22, 2012, 06:39:22 PM
 #8

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".

Welcome to my bitcoin mining pool: https://deepbit.net - Both payment schemes (including PPS), instant payout, no invalid blocks !
ICBIT Trading platform : USD/BTC futures trading, Bitcoin difficulty futures (NEW!). Third year in bitcoin business.
redditorrex
Sr. Member
****
Offline Offline

Activity: 280
Merit: 250


Nom Nom Nom


View Profile WWW
May 22, 2012, 06:53:33 PM
 #9

Watching.
I would be nice, but it is somewhat irrelevant
But if someone wants to write up a standard MtRed would support it.

Reddit Mining Team - MtRed.com = Pure PPS + #00GH/s + LP(+) + AutoPay&InstaPay + Audio Notifications
Find us in #mtred @ irc.freenode.net
DrHaribo
Legendary
*
Offline Offline

Activity: 2730
Merit: 1034


Needs more jiggawatts


View Profile WWW
May 22, 2012, 07:05:20 PM
 #10

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.

▶▶▶ bitminter.com 2011-2020 ▶▶▶ pool.xbtodigital.io 2023-
P_Shep (OP)
Legendary
*
Offline Offline

Activity: 1795
Merit: 1198


This is not OK.


View Profile
May 22, 2012, 07:27:24 PM
Last edit: May 22, 2012, 07:51:45 PM by P_Shep
 #11

Good to see my pro-active attempt gained some interest (Sorry if it was spammy!) Grin

OK, how about something like this:
(We'll leave workers and previous blocks for later versions.)

block =
{
    "duration" = <seconds>,
    "shares_total" = <total shares submitted so far for round>,
    "shares_submitted" = <shares submitted by user (all workers)>,
    "reward" = <estimated reward for current round or actual reward for previous rounds in Satoshis>
}

user =
{
    "API" = 1.0.0
    "current_round" = {<active block (as defined above)>},
    "hash_rate" = <current hash rate in MH/s for all workers - implementation pool dependent>,
    "last_activity" = <last submitted share time in unix time>,
    "confirmed_reward" = <confirmed reward (>=120 valid blocks) in Satoshis>,
    "unconfirmed_reward" = <unconfirmed reward (<120 valid blocks) in Satoshis>,
    "total_payout" = <total amount of BTC payed out to user (could be reset by user? - up to pool)>,
    "last_payout_value" = <value of last payout in Satoshis>,
    "last_payout_time" = <time of last payout in unix time>,
    "send_threshold" = <min confirmed reward before auto payout in Satoshis. 0 for no auto payment>,
    "workers" = {<TBC>}
}

Some elements take from Slush here.

So to retrieve BTC info, the URL would be something like:
http://<pool>/api.php?key=<API key>&currency=btc
or
http://<pool>/json/btc/<API key>

Then namecoin stats would be retrieved separately.
No real need (that I can think of) for URLs to be common/deterministic, down to the pool operator I should say.
At my end, I'd just use the entire URL in Anubis and deal with the data, not try and form the url.

 
Inaba
Legendary
*
Offline Offline

Activity: 1260
Merit: 1000



View Profile WWW
May 22, 2012, 08:14:27 PM
 #12

https://bitcointalk.org/index.php?topic=83027.msg915200#msg915200

If you're searching these lines for a point, you've probably missed it.  There was never anything there in the first place.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!