|
|
|
@ -355,7 +355,7 @@ transaction fees he'll attempt to((("bitcoins", "mining", "miners, purpose of",
|
|
|
|
|
|
|
|
|
|
==== The Coinbase Transaction
|
|
|
|
|
|
|
|
|
|
The first transaction in any
|
|
|
|
|
The ((("bitcoins", "mining", "coinbase transactions", id="bitcoin-mining-coinbase")))((("mining", "coinbase transactions", id="mining-coinbase")))((("nodes", "miner nodes", "coinbase transactions", id="nodes-miner-coinbase")))((("coinbase transactions", id="coinbase")))((("transactions", "coinbase", id="transaction-coinbase")))first transaction in any
|
|
|
|
|
block is a special transaction, called a _coinbase transaction_. This
|
|
|
|
|
transaction is constructed by Jing's node and pays out his _reward_ for
|
|
|
|
|
the mining effort.
|
|
|
|
@ -562,7 +562,7 @@ identifying the mining pool.
|
|
|
|
|
The first few bytes of the coinbase used to be arbitrary, but that is no
|
|
|
|
|
longer the case. As per BIP34, version-2 blocks (blocks with the
|
|
|
|
|
version field set to 2 or higher) must contain the block height as a script
|
|
|
|
|
"push" operation in the beginning of the coinbase field.
|
|
|
|
|
"push" operation in the beginning of the ((("bitcoins", "mining", "coinbase transactions", startref="bitcoin-mining-coinbase")))((("mining", "coinbase transactions", startref="mining-coinbase")))((("nodes", "miner nodes", "coinbase transactions", startref="nodes-miner-coinbase")))((("coinbase transactions", startref="coinbase")))((("transactions", "coinbase", startref="transaction-coinbase")))coinbase field.
|
|
|
|
|
|
|
|
|
|
=== Constructing the Block Header
|
|
|
|
|
|
|
|
|
|