From 5dc62f555b3afc3a8aa2ecc2a78aceb5746a92d1 Mon Sep 17 00:00:00 2001 From: clenser Date: Tue, 17 Oct 2023 21:16:25 +0000 Subject: [PATCH] Edited ch12_mining.adoc with Atlas code editor --- ch12_mining.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch12_mining.adoc b/ch12_mining.adoc index 2c62d1f4..9d92c07a 100644 --- a/ch12_mining.adoc +++ b/ch12_mining.adoc @@ -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