|
|
|
@ -366,7 +366,7 @@ wallet application creates the transaction outputs (payments).
|
|
|
|
|
|
|
|
|
|
==== Creating the Outputs
|
|
|
|
|
|
|
|
|
|
A transaction output is
|
|
|
|
|
A transaction output((("outputs", "constructing transactions"))) is
|
|
|
|
|
created with a
|
|
|
|
|
script that says something like, "This output is paid to whoever can
|
|
|
|
|
present a signature from the key corresponding to Bob's public address."
|
|
|
|
@ -383,7 +383,7 @@ transaction as the payment to Bob. Essentially, Alice's wallet breaks
|
|
|
|
|
her funds into two outputs: one to Bob and one back to herself. She can
|
|
|
|
|
then spend the change output in a subsequent transaction.
|
|
|
|
|
|
|
|
|
|
Finally, for the transaction to be processed by the network in a timely
|
|
|
|
|
Finally, for the transaction to be processed by the network in a((("transaction fees"))) timely
|
|
|
|
|
fashion, Alice's wallet application will add a small fee. The fee is not
|
|
|
|
|
explicitly stated in the transaction; it is implied by the difference in value between
|
|
|
|
|
inputs and outputs. This _transaction fee_ is collected by the
|
|
|
|
|