From e8f02aefc6b23b9d248b616f44e0ca8c5515eabd Mon Sep 17 00:00:00 2001 From: clenser Date: Tue, 17 Oct 2023 21:18:08 +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 9d92c07a..f823f416 100644 --- a/ch12_mining.adoc +++ b/ch12_mining.adoc @@ -378,7 +378,7 @@ reward. ==== Coinbase Reward and Fees -To construct the +To construct((("rewards", "in coinbase transactions", secondary-sortas="coinbase transactions", id="reward-coinbase")))((("transaction fees", "in coinbase transactions", secondary-sortas="coinbase transactions", id="transaction-fee-coinbase"))) the coinbase transaction, Jing's node first calculates the total amount of transaction fees: @@ -441,7 +441,7 @@ If Jing's mining node writes the coinbase transaction, what stops Jing from "rewarding" himself 100 or 1,000 bitcoin? The answer is that an inflated reward would result in the block being deemed invalid by everyone else, wasting Jing's electricity used for Proof-of-Work. Jing -only gets to spend the reward if the block is accepted by everyone. +only gets to spend the reward if the block is accepted by ((("rewards", "in coinbase transactions", secondary-sortas="coinbase transactions", startref="reward-coinbase")))((("transaction fees", "in coinbase transactions", secondary-sortas="coinbase transactions", startref="transaction-fee-coinbase")))everyone. ==== ==== Structure of the Coinbase Transaction