BIP PoolAPI: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
← Older edit
Luke-jr (talk | contribs)
Clerks, Administrators, Editors
3,074 edits
No edit summary
Luke-jr (talk | contribs)
Clerks, Administrators, Editors
3,074 edits
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
                        {{bip}}
<pre>
  BIP: ?
  Title: JSON Pool Information API
  Author: Paul Sheppard <shepsoft@gmail.com> and Luke Dashjr <luke+bip22@dashjr.org>
  Status: Draft
  Type: Standards Track
  Created: 22-05-2012
</pre>
==Abstract==
This BIP aims to create a standard API for pool statistics.
==Specification==
* All time keys are seconds since Jan 1 1970 midnight UTC.
* Hashrate is measured in full block hashes per second. So if a full block proof-of-work requires two rounds of SHA256 (as it does with Bitcoin today), each two rounds counts only as a single hash.
* Currencies are always represented in the smallest divisible part of the currency. eg, for USD this is 1 cent and for Bitcoin this is 0.00000001 BTC
===Object Formats===
{| class="wikitable"
{| class="wikitable"
! Key !! Type !! Description
! Key !! Type !! Description
Line 17: Line 38:
|-
|-
| hashrate || Number || total hashrate of all mining in the organizational pool
| hashrate || Number || total hashrate of all mining in the organizational pool
|-
| message || String || whatever the pool wants to tell us
|-
| minercount || Number || total number of active miners
|-
|-
| miners || Array of Objects || information of specific miners
| miners || Array of Objects || information of specific miners
|-
| workercount || Number || total number of active workers
|-
|-
!colspan='3'| Collaborative pool
!colspan='3'| Collaborative pool
Line 28: Line 55:
| hashrate || Number || total hashrate of all mining in the same collaborative pool
| hashrate || Number || total hashrate of all mining in the same collaborative pool
|-
|-
| roundbegin || Number || time the current round began
| message || String || whatever the pool wants to tell us
|-
|-
| roundshares || Number || number of shares submitted to the current round
| round || Object || information about the current round
|-
|-
| fee || Number || fee (0.01 = 1%)
| fee || Number || fee (0.01 = 1%)
|-
|-
| rewardalgo || String || reward algorithm identifier
| rewardalgo || String || reward algorithm identifier
|-
| minercount || Number || total number of active miners
|-
|-
| miners || Array of Objects || information of specific miners
| miners || Array of Objects || information of specific miners
|-
| time || Number || time as the poolserver sees it
|-
| workercount || Number || total number of active workers
|-
!colspan='3'| Round
|-
! Key !! Type !! Description
|-
| id || String || unique identifier for the round
|-
| begintime || Number || time the current round began
|-
| shares || Object || number of shares submitted to the current round
|-
| network || String || which network the round is relevant for
|-
| parent || String || network-specific identifier for the base of the current round
|-
!colspan='3'| Shares
|-
! Key !! Type !! Description
|-
| accepted || Number || number of accepted shares
|-
| * || Number || any [[BIP 0022#Example Rejection Reasons|rejection reason]] may be a key; value is number of shares
|-
|-
!colspan='3'| Individual miner or worker
!colspan='3'| Individual miner or worker
Line 45: Line 100:
|-
|-
| name || String || human-readable identifier for miner
| name || String || human-readable identifier for miner
|-
| message || String || whatever the pool wants to tell us
|-
|-
| balances || Array of Objects || balance information
| balances || Array of Objects || balance information
|-
| fee || Number || fee (0.01 = 1%)
|-
|-
| hashrate || Number || total hashrate of all mining in the same collaborative pool
| hashrate || Number || total hashrate of all mining in the same collaborative pool
Line 52: Line 111:
| lastactive || Number || time the miner was last seen active
| lastactive || Number || time the miner was last seen active
|-
|-
| roundshares || Number || number of shares submitted to the current round
| rewardalgo || String || reward algorithm identifier
|-
| sharesround || Object || information on shares submitted to the current round
|-
| sharesuser || Object || information on shares submitted since last user reset
|-
| sharestotal || Object || information on shares submitted for all time
|-
|-
| workers || Array of Objects || information of specific workers
| workers || Array of Objects || information of specific workers
Line 63: Line 128:
|-
|-
| balance || Number || amount currently stored at the pool
| balance || Number || amount currently stored at the pool
|-
| unconfirmed || Number || amount currently waiting for confirmations
|-
|-
| estimate || Number || amount expected reward for the current round
| estimate || Number || amount expected reward for the current round
|-
| fee || Number || fee (0.01 = 1%)
|-
|-
| paid || Number || amount that has been paid out ever
| paid || Number || amount that has been paid out ever
Line 71: Line 140:
|-
|-
| lastpaytime || Number || time of last payout
| lastpaytime || Number || time of last payout
|-
| autopay || Number || minimum amount before autopayout
|-
| autopayto || String || address for autopayouts
|}
|}


Line 82: Line 155:
|-
|-
| fiat || Pool-specific "play money" (eg, SMPPS "extra credit")
| fiat || Pool-specific "play money" (eg, SMPPS "extra credit")
|}
Networks:
{| class="wikitable"
! Network name !! Description
|-
| Bitcoin || Bitcoin blockchain
|-
| Bitcoin address || Searching for vanity Bitcoin addresses
|-
| Namecoin || Namecoin blockchain
|}
|}


Line 94: Line 178:
| PPS || Pay Per Share
| PPS || Pay Per Share
|-
|-
| PPS/SM || Shared Maximum Pay Per Share
| SMPPS || Shared Maximum Pay Per Share
|-
|-
| Score ||
| Score ||
|-
|-
| Score/Geo || Geometric Method
| Geo || Geometric Method
|-
|-
| Score/Geo/Dbl || Double Geometric Method
| DGM || Double Geometric Method
|}
|}


Example:
===Example===
<pre>
<pre>
{
{
Line 109: Line 193:
"group": {
"group": {
"name": "Eligius",
"name": "Eligius",
"hashrate": 600000000000
"hashrate": 600000000000,
"message": "Welcome to Eligius! Enjoy :)"
},
},
"collab": [
"collab": [
Line 115: Line 200:
"name": "Eligius-Ra",
"name": "Eligius-Ra",
"hashrate": 550000000000,
"hashrate": 550000000000,
"roundbegin": 1337719877.959086,
"time": 1337729874.2489,
"roundshares": 423433,
"workercount": 5423,
"round": {
"begintime": 1337719877.959086,
"blockchain": "Bitcoin",
"blockparent": "00000000000001c536f8865bd2be554372fa149eb88fb1c096f475e1c9cd8176",
"shares": {
"accepted": 423433,
"stale-prevblk": 92,
"duplicate": 3
}
},
"fee": 0,
"fee": 0,
"rewardalgo": "SMPPS",
"rewardalgo": "SMPPS",
Line 139: Line 234:
"hashrate": 1382848482,
"hashrate": 1382848482,
"lastactive": 1337783882.423086,
"lastactive": 1337783882.423086,
"roundshares": 832,
"sharesround": {
"accepted": 832
},
"workers": [
"workers": [
{
{
Line 146: Line 243:
"hashrate": 378483883,
"hashrate": 378483883,
"lastactive": 1337783882.423086,
"lastactive": 1337783882.423086,
"roundshares": 100,
"sharesround": {
"accepted": 100
}
},
},
{
{
Line 153: Line 252:
"hashrate": 832942393,
"hashrate": 832942393,
"lastactive": 1337783882.423086,
"lastactive": 1337783882.423086,
"roundshares": 600,
"sharesround": {
"accepted": 600
}
},
},
{
{
Line 160: Line 261:
"hashrate": 371422206,
"hashrate": 371422206,
"lastactive": 1337783882.423086,
"lastactive": 1337783882.423086,
"roundshares": 232,
"sharesround": {
"accepted": 232
}
}
}
]
]
Line 167: Line 270:
]
]
}</pre>
}</pre>
==Motivation==
Moving forward with bitcoin it is important to make all aspects as user friendly as possible.
==Rationale==
This BIP allows the creators of Apps and Web GUIs for pool monitoring a common interface to use, as opposed to dealing with a differing interface for each pool.
==Backwards Compatibility==
As an emerging standard, backwards comparability is not applicable. However forward comparability should be maintained. Any future incompatibilities shall be identified by the 'API_version' number.

Latest revision as of 03:21, 7 June 2012

This page describes a BIP (Bitcoin Improvement Proposal).
Please see BIP 2 for more information about BIPs and creating them. Please do not just create a wiki page.

 
  BIP: ?
  Title: JSON Pool Information API
  Author: Paul Sheppard <shepsoft@gmail.com> and Luke Dashjr <luke+bip22@dashjr.org>
  Status: Draft
  Type: Standards Track
  Created: 22-05-2012

Abstract

This BIP aims to create a standard API for pool statistics.

Specification

  • All time keys are seconds since Jan 1 1970 midnight UTC.
  • Hashrate is measured in full block hashes per second. So if a full block proof-of-work requires two rounds of SHA256 (as it does with Bitcoin today), each two rounds counts only as a single hash.
  • Currencies are always represented in the smallest divisible part of the currency. eg, for USD this is 1 cent and for Bitcoin this is 0.00000001 BTC

Object Formats

Key Type Description
Root
version Number always 1
group Object information about the organizational pool
collab Array of Objects information about each collaborative pool
Organizational pool
Key Type Description
name String human-readable identifier for organizational pool
hashrate Number total hashrate of all mining in the organizational pool
message String whatever the pool wants to tell us
minercount Number total number of active miners
miners Array of Objects information of specific miners
workercount Number total number of active workers
Collaborative pool
Key Type Description
name String human-readable identifier for collaborative pool
hashrate Number total hashrate of all mining in the same collaborative pool
message String whatever the pool wants to tell us
round Object information about the current round
fee Number fee (0.01 = 1%)
rewardalgo String reward algorithm identifier
minercount Number total number of active miners
miners Array of Objects information of specific miners
time Number time as the poolserver sees it
workercount Number total number of active workers
Round
Key Type Description
id String unique identifier for the round
begintime Number time the current round began
shares Object number of shares submitted to the current round
network String which network the round is relevant for
parent String network-specific identifier for the base of the current round
Shares
Key Type Description
accepted Number number of accepted shares
* Number any rejection reason may be a key; value is number of shares
Individual miner or worker
Key Type Description
id String unique identifier for a miner's account (shared across collaborative pools)
name String human-readable identifier for miner
message String whatever the pool wants to tell us
balances Array of Objects balance information
fee Number fee (0.01 = 1%)
hashrate Number total hashrate of all mining in the same collaborative pool
lastactive Number time the miner was last seen active
rewardalgo String reward algorithm identifier
sharesround Object information on shares submitted to the current round
sharesuser Object information on shares submitted since last user reset
sharestotal Object information on shares submitted for all time
workers Array of Objects information of specific workers
Balance info
Key Type Description
currency String currency of balance
balance Number amount currently stored at the pool
unconfirmed Number amount currently waiting for confirmations
estimate Number amount expected reward for the current round
fee Number fee (0.01 = 1%)
paid Number amount that has been paid out ever
lastpay Number amount of last payout
lastpaytime Number time of last payout
autopay Number minimum amount before autopayout
autopayto String address for autopayouts

Currencies:

Currency name Description
Bitcoin Bitcoins (in Satoshis)
Namecoin Namecoins
fiat Pool-specific "play money" (eg, SMPPS "extra credit")

Networks:

Network name Description
Bitcoin Bitcoin blockchain
Bitcoin address Searching for vanity Bitcoin addresses
Namecoin Namecoin blockchain

Reward algorithms:

Algorithm name Description
Prop Proportional
PPLNS Pay Per Last N Shares
PPS Pay Per Share
SMPPS Shared Maximum Pay Per Share
Score
Geo Geometric Method
DGM Double Geometric Method

Example

{
	"version": 1,
	"group": {
		"name": "Eligius",
		"hashrate": 600000000000,
		"message": "Welcome to Eligius! Enjoy :)"
	},
	"collab": [
		{
			"name": "Eligius-Ra",
			"hashrate": 550000000000,
			"time": 1337729874.2489,
			"workercount": 5423,
			"round": {
				"begintime": 1337719877.959086,
				"blockchain": "Bitcoin",
				"blockparent": "00000000000001c536f8865bd2be554372fa149eb88fb1c096f475e1c9cd8176",
				"shares": {
					"accepted": 423433,
					"stale-prevblk": 92,
					"duplicate": 3
				}
			},
			"fee": 0,
			"rewardalgo": "SMPPS",
			"miners": [
				"id": "16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pkW",
				"name": "Luke-Jr",
				"balances": [
					{
						"currency": "Bitcoin",
						"balance": 167476453,
						"estimate": 14761828,
						"paid": 5800000000,
						"lastpay": 67423840,
						"lastpaytime": 1337713832.25908
					},
					{
						"currency": "fiat",
						"balance": 9342224,
						"estimate": 39433
					}
				],
				"hashrate": 1382848482,
				"lastactive": 1337783882.423086,
				"sharesround": {
					"accepted": 832
				},
				"workers": [
					{
						"id": "16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pkW_Icarus",
						"name": "Luke-Jr's Icarus :)",
						"hashrate": 378483883,
						"lastactive": 1337783882.423086,
						"sharesround": {
							"accepted": 100
						}
					},
					{
						"id": "16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pkW_BFL",
						"name": "Luke-Jr's BitForce Single :D",
						"hashrate": 832942393,
						"lastactive": 1337783882.423086,
						"sharesround": {
							"accepted": 600
						}
					},
					{
						"id": "16kNKa7WUg8QAPFy8dJRv7USSu2fAG2pkW_6870",
						"name": "Luke-Jr's Radeon 6870",
						"hashrate": 371422206,
						"lastactive": 1337783882.423086,
						"sharesround": {
							"accepted": 232
						}
					}
				]
			]
		}
	]
}

Motivation

Moving forward with bitcoin it is important to make all aspects as user friendly as possible.

Rationale

This BIP allows the creators of Apps and Web GUIs for pool monitoring a common interface to use, as opposed to dealing with a differing interface for each pool.

Backwards Compatibility

As an emerging standard, backwards comparability is not applicable. However forward comparability should be maintained. Any future incompatibilities shall be identified by the 'API_version' number.

Retrieved from "https://en.bitcoin.it/w/index.php?title=BIP_PoolAPI&oldid=27516"