Difference between revisions of "Coinbase"
(Created page with "The '''coinbase''' is the content of the 'input' of a generation transaction. While regular transactions use the 'inputs' section to refer to their parent transaction outp...") |
Todd Price (talk | contribs) |
||
| (22 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | '''Coinbase''' is the special name given to the first transaction in every block. These can also be called 'Generation Transactions'. | |
| − | The coinbase can | + | The winning Miner creates this special transaction as part of the block templating process. |
| − | + | ||
| + | A coinbase transaction follows the same format as a normal transaction, except: | ||
| + | * It has exactly one txin. | ||
| + | * This txin's prevout hash is 0000...0000. | ||
| + | * This txin's prevout [[index]] is 0xFFFFFFFF. | ||
| + | * The txin's prevout script is an arbitrary byte array which has historically been used by Miners to signal identity and pass messages from block winning nodes to the rest of the network. | ||
| + | * The sum of the values of all txout's cannot exceed the total of the [[Miner subsidy]] and the mining fees paid by all other transactions included in the block. | ||
| + | |||
| + | A part of the coinbase can also used as an 'extra nonce' during the block discovery process due to a single ASIC Miner being able to test more combinations than allowed for, in the 2^32 possible combinations that changing the nonce in the block header can create. The extra nonce field is incremented in the Coinbase transaction, which requires that a small number of hashes in the merkle tree are updated, changing the [[Merkle root]] in the [[block header]] allowing for a further 2^32 possible block hashes to be attempted. | ||
| + | |||
| + | A Coinbase transaction can have as many outputs attached as are needed by the miner. These can be used for second layer functions including: | ||
| + | *[[Merchant API]], otherwise known as [[MAPI]], which allows the winning Miner to provide a dynamically accessible transaction pricing service enabling users to request pricing and transaction broadcast services from miners on the network. | ||
| + | *[[MinerID]] also uses the Coinbase transaction to present information to the network such as node identity, MAPI access points and more. This data will use standard formats such that user wallets shall be able to read and parse the information, giving them up-to-date knowledge of which nodes are competing on the network and more. | ||
| + | |||
| + | Due to some early problems with blocks containing only a coinbase transaction with an identical coinbase text and outputs generating coinbase transactions with identical [[TXID|TXIDs]], miners agreed through consensus to begin enforcing [https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki BIP 0034] as a [[Protocol|protocol rule]]. This change mandated that the block height value be specified in the first item of the coinbase transaction. Prior to this, the coinbase script size was between 2 and 100 bytes. Currently the minimum length is 4 bytes which is needed to hold the blockheight in a [[VarInt]]. The maximum value storable in 3 bytes is 16,777,215 so with the generating blocks at a rate of approximately 59,000 per year so if this level of network activity is sustained then from approximately the year 2,300 the minimum length of a coinbase script size will need to increase to 5 bytes. | ||
Latest revision as of 04:26, 25 April 2022
Coinbase is the special name given to the first transaction in every block. These can also be called 'Generation Transactions'.
The winning Miner creates this special transaction as part of the block templating process.
A coinbase transaction follows the same format as a normal transaction, except:
- It has exactly one txin.
- This txin's prevout hash is 0000...0000.
- This txin's prevout index is 0xFFFFFFFF.
- The txin's prevout script is an arbitrary byte array which has historically been used by Miners to signal identity and pass messages from block winning nodes to the rest of the network.
- The sum of the values of all txout's cannot exceed the total of the Miner subsidy and the mining fees paid by all other transactions included in the block.
A part of the coinbase can also used as an 'extra nonce' during the block discovery process due to a single ASIC Miner being able to test more combinations than allowed for, in the 2^32 possible combinations that changing the nonce in the block header can create. The extra nonce field is incremented in the Coinbase transaction, which requires that a small number of hashes in the merkle tree are updated, changing the Merkle root in the block header allowing for a further 2^32 possible block hashes to be attempted.
A Coinbase transaction can have as many outputs attached as are needed by the miner. These can be used for second layer functions including:
- Merchant API, otherwise known as MAPI, which allows the winning Miner to provide a dynamically accessible transaction pricing service enabling users to request pricing and transaction broadcast services from miners on the network.
- MinerID also uses the Coinbase transaction to present information to the network such as node identity, MAPI access points and more. This data will use standard formats such that user wallets shall be able to read and parse the information, giving them up-to-date knowledge of which nodes are competing on the network and more.
Due to some early problems with blocks containing only a coinbase transaction with an identical coinbase text and outputs generating coinbase transactions with identical TXIDs, miners agreed through consensus to begin enforcing BIP 0034 as a protocol rule. This change mandated that the block height value be specified in the first item of the coinbase transaction. Prior to this, the coinbase script size was between 2 and 100 bytes. Currently the minimum length is 4 bytes which is needed to hold the blockheight in a VarInt. The maximum value storable in 3 bytes is 16,777,215 so with the generating blocks at a rate of approximately 59,000 per year so if this level of network activity is sustained then from approximately the year 2,300 the minimum length of a coinbase script size will need to increase to 5 bytes.