BIP 0022 - Revision history

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0022.mediawiki

2019-09-24T17:58:38Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0022.mediawiki

Show changes

934: Undo revision 44926 by Luke-jr (talk)

2016-03-29T17:10:57Z

Undo revision 44926 by Luke-jr (talk)

Show changes

Luke-jr: Undo revision 42913 by Witchspace (talk)

2014-03-11T23:57:30Z

Undo revision 42913 by Witchspace (talk)

Show changes

Wumpus: Move to github

2013-12-06T07:47:35Z

Move to github

Show changes

Luke-jr: /* Block Template Request */ Clarify required keys

2012-11-17T20:35:51Z

Block Template Request: Clarify required keys

Luke-jr: Status can now be promoted to Accepted since we have actual use

2012-09-15T04:13:22Z

Status can now be promoted to Accepted since we have actual use

← Older revision		Revision as of 04:13, 15 September 2012
Line 5:		Line 5:
	Title: getblocktemplate - Fundamentals		Title: getblocktemplate - Fundamentals
	Author: Luke Dashjr <luke+bip22@dashjr.org>		Author: Luke Dashjr <luke+bip22@dashjr.org>
	Status: ~~Draft~~		Status: Accepted
	Type: Standards Track		Type: Standards Track
	Created: 28-02-2012		Created: 28-02-2012

Luke-jr: /* Reference Implementation */

2012-09-10T19:16:14Z

Reference Implementation

← Older revision		Revision as of 19:16, 10 September 2012
Line 235:		Line 235:
	==Reference Implementation==		==Reference Implementation==

	* [https://gitorious.org/bitcoin/eloipool Eloipool]		* [https://gitorious.org/bitcoin/eloipool Eloipool (server)]
	* [https://github.com/bitcoin/bitcoin/pull/936/files bitcoind]		* [http://gitorious.org/bitcoin/libblkmaker libblkmaker (client)]
			* [https://github.com/bitcoin/bitcoin/pull/936/files bitcoind (minimal server)]

	==See Also==		==See Also==

Luke-jr: /* Optional: Template Tweaking */ Allow clients to provide their maximum version supported

2012-09-05T02:49:52Z

Optional: Template Tweaking: Allow clients to provide their maximum version supported

← Older revision		Revision as of 02:49, 5 September 2012
Line 162:		Line 162:
	\|-		\|-
	\| sizelimit \|\| Number or Boolean \|\| maximum number of bytes to use for the entire block		\| sizelimit \|\| Number or Boolean \|\| maximum number of bytes to use for the entire block
			\|-
			\| maxversion \|\| Number \|\| highest block version number supported
	\|}		\|}

Luke-jr: /* Optional: Long Polling */ Clarify uniqueness of "longpollid"

2012-09-05T01:55:56Z

Optional: Long Polling: Clarify uniqueness of "longpollid"

← Older revision		Revision as of 01:55, 5 September 2012
Line 123:		Line 123:
	! Key !! Type !! Description		! Key !! Type !! Description
	\|-		\|-
	\| longpollid \|\| String \|\| ~~unique~~ identifier for long poll request; MUST be omitted if the server does not support long polling		\| longpollid \|\| String \|\| identifier for long poll request; MUST be omitted if the server does not support long polling
	\|-		\|-
	\| longpolluri \|\| String \|\| if provided, an alternate URI to use for long poll requests		\| longpolluri \|\| String \|\| if provided, an alternate URI to use for long poll requests
Line 130:		Line 130:
	\|}		\|}

	If the server supports long polling, it MUST include a "longpollid" key in block templates.		If the server supports long polling, it MUST include a "longpollid" key in block templates, and it MUST be unique for each event:
			any given "longpollid" should check for only one condition and not be reused.
			For example, a server which has a long poll wakeup only for new blocks might use the previous block hash.
			However, clients should not assume the "longpollid" has any specific meaning.
	It MAY supply the "longpolluri" key with a relative or absolute URI, which MAY specify a completely different resource than the original connection, including port number.		It MAY supply the "longpolluri" key with a relative or absolute URI, which MAY specify a completely different resource than the original connection, including port number.
	If "longpolluri" is provided by the server, clients MUST only attempt to use that URI for longpoll requests.		If "longpolluri" is provided by the server, clients MUST only attempt to use that URI for longpoll requests.

Luke-jr: Undo revision 30164 by Genjix (talk)

2012-08-28T03:48:37Z

Undo revision 30164 by Genjix (talk)

← Older revision		Revision as of 03:48, 28 August 2012
Line 5:		Line 5:
	Title: getblocktemplate - Fundamentals		Title: getblocktemplate - Fundamentals
	Author: Luke Dashjr <luke+bip22@dashjr.org>		Author: Luke Dashjr <luke+bip22@dashjr.org>
	Status: ~~Accepted~~		Status: Draft
	Type: Standards Track		Type: Standards Track
	Created: 28-02-2012		Created: 28-02-2012

← Older revision		Revision as of 20:35, 17 November 2012
Line 25:		Line 25:
	Block template creation can be influenced by various parameters:		Block template creation can be influenced by various parameters:
	{\| class="wikitable"		{\| class="wikitable"
	!colspan=3\|template request		!colspan=4\|template request
	\|-		\|-
	! Key !! Type !! Description		! Key !! Required !! Type !! Description
	\|-		\|-
	\| capabilities \|\| Array of Strings \|\| SHOULD contain a list of the following, to indicate client-side support: [[#Optional: Long Polling\|"longpoll"]], "coinbasetxn", "coinbasevalue", [[BIP 0023#Block Proposal\|"proposal"]], [[BIP 0023#Logical Services\|"serverlist"]], "workid", and any of the [[BIP 0023#Mutations\|mutations]]		\| capabilities \|\| {{No}} \|\| Array of Strings \|\| SHOULD contain a list of the following, to indicate client-side support: [[#Optional: Long Polling\|"longpoll"]], "coinbasetxn", "coinbasevalue", [[BIP 0023#Block Proposal\|"proposal"]], [[BIP 0023#Logical Services\|"serverlist"]], "workid", and any of the [[BIP 0023#Mutations\|mutations]]
	\|-		\|-
	\| mode \|\| String \|\| MUST be "template" or omitted		\| mode \|\| {{No}} \|\| String \|\| MUST be "template" or omitted
	\|}		\|}

	getblocktemplate MUST return a JSON Object containing the following keys:		getblocktemplate MUST return a JSON Object containing the following keys:
	{\| class="wikitable"		{\| class="wikitable"
	!colspan=3\| template		!colspan=4\| template
	\|-		\|-
	! Key !! Type !! Description		! Key !! Required !! Type !! Description
	\|-		\|-
	\| bits \|\| String \|\| the compressed difficulty in hexadecimal		\| bits \|\| {{Yes}} \|\| String \|\| the compressed difficulty in hexadecimal
	\|-		\|-
	\| curtime \|\| Number \|\| the current time as seen by the server (recommended for block time) - note this is not necessarily the system clock, and must fall within the mintime/maxtime rules		\| curtime \|\| {{Yes}} \|\| Number \|\| the current time as seen by the server (recommended for block time) - note this is not necessarily the system clock, and must fall within the mintime/maxtime rules
	\|-		\|-
	\| height \|\| Number \|\| the height of the block we are looking for		\| height \|\| {{Yes}} \|\| Number \|\| the height of the block we are looking for
	\|-		\|-
	\| previousblockhash \|\| String \|\| the hash of the previous block, in big-endian hexadecimal		\| previousblockhash \|\| {{Yes}} \|\| String \|\| the hash of the previous block, in big-endian hexadecimal
	\|-		\|-
	\| sigoplimit \|\| Number \|\| number of sigops allowed in blocks		\| sigoplimit \|\| {{No}} \|\| Number \|\| number of sigops allowed in blocks
	\|-		\|-
	\| sizelimit \|\| Number \|\| number of bytes allowed in blocks		\| sizelimit \|\| {{No}} \|\| Number \|\| number of bytes allowed in blocks
	\|-		\|-
	\| transactions \|\| Array of Objects \|\| Objects containing [[#Transactions Object Format\|information for Bitcoin transactions]] (excluding coinbase)		\| transactions \|\| {{Yes\|Should}} \|\| Array of Objects \|\| Objects containing [[#Transactions Object Format\|information for Bitcoin transactions]] (excluding coinbase)
	\|-		\|-
	\| version \|\| Number \|\| always 1 or 2 (at least for bitcoin) - clients MUST understand the implications of the version they use (eg, comply with [[BIP 0034]] for version 2)		\| version \|\| {{Yes}} \|\| Number \|\| always 1 or 2 (at least for bitcoin) - clients MUST understand the implications of the version they use (eg, comply with [[BIP 0034]] for version 2)
	\|-		\|-
	\| coinbaseaux \|\| Object \|\| data that SHOULD be included in the coinbase's scriptSig content. Only the values (hexadecimal byte-for-byte) in this Object should be included, not the keys. This does not include the block height, which is required to be included in the scriptSig by [[BIP 0034]]. It is advisable to encode values inside "PUSH" opcodes, so as to not inadvertantly expend SIGOPs (which are counted toward limits, despite not being executed).		\| coinbaseaux \|\| {{No}} \|\| Object \|\| data that SHOULD be included in the coinbase's scriptSig content. Only the values (hexadecimal byte-for-byte) in this Object should be included, not the keys. This does not include the block height, which is required to be included in the scriptSig by [[BIP 0034]]. It is advisable to encode values inside "PUSH" opcodes, so as to not inadvertantly expend SIGOPs (which are counted toward limits, despite not being executed).
	\|-		\|-
	\| coinbasetxn \|\| Object \|\| [[#Transactions Object Format\|information for coinbase transaction]]		\| coinbasetxn \|\| {{Patch\|this or ↓}} \|\| Object \|\| [[#Transactions Object Format\|information for coinbase transaction]]
	\|-		\|-
	\| coinbasevalue \|\| Number \|\| total funds available for the coinbase (in Satoshis)		\| coinbasevalue \|\| {{Patch\|this or ↑}} \|\| Number \|\| total funds available for the coinbase (in Satoshis)
	\|-		\|-
	\| workid \|\| String \|\| if provided, this value must be returned with results (see [[#Block Submission\|Block Submission]])		\| workid \|\| {{No}} \|\| String \|\| if provided, this value must be returned with results (see [[#Block Submission\|Block Submission]])
	\|}		\|}