mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-13 19:38:56 +00:00
Edited ch12_mining.adoc with Atlas code editor
This commit is contained in:
parent
5dc62f555b
commit
e8f02aefc6
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user