|
|
|
@ -435,9 +435,9 @@ output. Alice will therefore "encumber" the output value with a demand
|
|
|
|
|
for a signature from Bob.
|
|
|
|
|
|
|
|
|
|
This transaction will also include a second output, because Alice's
|
|
|
|
|
funds are in the form of a 0.10 BTC output, too much money for the 0.015
|
|
|
|
|
BTC podcast. Alice will need 0.085 BTC in change. Alice's change
|
|
|
|
|
payment is created by Alice's wallet as an output in the very same
|
|
|
|
|
funds are contain more money than the cost of the
|
|
|
|
|
podcast. Alice's change
|
|
|
|
|
output is created in the very same
|
|
|
|
|
transaction as the payment to Bob. Essentially, Alice's wallet breaks
|
|
|
|
|
her funds into two payments: one to Bob and one back to herself. She can
|
|
|
|
|
then use (spend) the change output in a subsequent transaction.
|
|
|
|
@ -445,11 +445,7 @@ then use (spend) the change output in a subsequent transaction.
|
|
|
|
|
Finally, for the transaction to be processed by the network in a timely
|
|
|
|
|
fashion, Alice's wallet application will add a small fee. This is not
|
|
|
|
|
explicit in the transaction; it is implied by the difference between
|
|
|
|
|
inputs and outputs. If instead of taking 0.085 in change, Alice creates
|
|
|
|
|
only 0.0845 as the second output, there will be 0.0005 BTC (half a
|
|
|
|
|
millibitcoin) left over. The input's 0.10 BTC is not fully spent with
|
|
|
|
|
the two outputs, because they will add up to less than 0.10. The
|
|
|
|
|
resulting difference is the _transaction fee_ that is collected by the
|
|
|
|
|
inputs and outputs. This _transaction fee_ is collected by the
|
|
|
|
|
miner as a fee for validating and including the transaction in a block
|
|
|
|
|
to be recorded on the blockchain.
|
|
|
|
|
|
|
|
|
@ -670,8 +666,8 @@ thereby making it more and more trusted by the network.
|
|
|
|
|
|
|
|
|
|
((("genesis block")))((("blocks", "genesis block")))((("blockchain
|
|
|
|
|
(the)", "genesis block")))In the diagram in <<block-alice1>>, we can
|
|
|
|
|
see block #277316, which contains Alice's transaction. Below it are
|
|
|
|
|
277,316 blocks (including block #0), linked to each other in a chain of
|
|
|
|
|
see block the block which contains Alice's transaction. Below it are
|
|
|
|
|
hundreds of thousands of blocks, linked to each other in a chain of
|
|
|
|
|
blocks (blockchain) all the way back to block #0, known as the _genesis
|
|
|
|
|
block_. Over time, as the "height" in blocks increases, so does the
|
|
|
|
|
computation difficulty for each block and the chain as a whole. The
|
|
|
|
@ -685,7 +681,7 @@ the process of mining and the way it builds trust in more detail in
|
|
|
|
|
startref="MACover02")))
|
|
|
|
|
|
|
|
|
|
[[block-alice1]]
|
|
|
|
|
.Alice's transaction included in block #277316
|
|
|
|
|
.Alice's transaction included in a block
|
|
|
|
|
image::images/mbc2_0209.png["Alice's transaction included in a block"]
|
|
|
|
|
|
|
|
|
|
=== Spending the Transaction
|
|
|
|
|