|
|
|
@ -294,16 +294,6 @@ always have only big bills. People subconsciously find a balance between
|
|
|
|
|
these two extremes, and bitcoin wallet developers strive to program this
|
|
|
|
|
balance.
|
|
|
|
|
|
|
|
|
|
((("transactions", "defined")))((("outputs and inputs",
|
|
|
|
|
"defined")))((("inputs", see="outputs and inputs")))In summary,
|
|
|
|
|
_transactions_ move value from _transaction inputs_ to _transaction
|
|
|
|
|
outputs_. An input is a reference to a previous transaction's output,
|
|
|
|
|
showing where the value is coming from. A transaction output directs a
|
|
|
|
|
specific value to a new owner's Bitcoin address and can include a change
|
|
|
|
|
output back to the original owner. Outputs from one transaction can be
|
|
|
|
|
used as inputs in a new transaction, thus creating a chain of ownership
|
|
|
|
|
as the value is moved from owner to owner (see <<blockchain-mnemonic>>).
|
|
|
|
|
|
|
|
|
|
==== Common Transaction Forms
|
|
|
|
|
|
|
|
|
|
The most common form of transaction is a simple payment from one address
|
|
|
|
|