Edited ch12_mining.adoc with Atlas code editor

7 months ago · 4d3ce9a184
parent e89ff93795
commit 4d3ce9a184
1 changed files with 2 additions and 2 deletions
--- a/ch12_mining.adoc
+++ b/ch12_mining.adoc
@ -378,7 +378,7 @@ reward.

 ==== Coinbase Reward and Fees

-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
+To construct((("rewards", 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 ((("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.
+only gets to spend the reward if the block is accepted by ((("rewards", startref="reward-coinbase")))((("transaction fees", "in coinbase transactions", secondary-sortas="coinbase transactions", startref="transaction-fee-coinbase")))everyone.
 ====

 ==== Structure of the Coinbase Transaction