mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-22 16:18:11 +00:00
Edited ch06_transactions.adoc with Atlas code editor
This commit is contained in:
parent
4b142b0a7d
commit
8da3c29ce9
@ -268,7 +268,7 @@ transaction and so we'll ((("transactions", "inputs", "length of list", startref
|
||||
[[outpoints]]
|
||||
==== Outpoint
|
||||
|
||||
A Bitcoin transaction is a request for full nodes to update their
|
||||
A Bitcoin ((("transactions", "inputs", "outpoint field", id="transaction-input-outpoint")))((("inputs", "outpoint field", id="input-transaction-outpoint")))((("outpoint field (transaction inputs)", id="outpoint")))transaction is a request for full nodes to update their
|
||||
database of coin ownership information. For Alice to transfer control
|
||||
of some of her bitcoins to Bob, she first needs to tell full nodes how
|
||||
to find the previous transfer where she received those bitcoins. Since
|
||||
@ -329,7 +329,7 @@ database that stores every unspent transaction output (UTXO) and
|
||||
essential metadata about it (like its confirmation block height). Each
|
||||
time a new block of transactions arrives, all of the outputs they spend
|
||||
are removed from the UTXO database and all of the outputs they create
|
||||
are added to the database.
|
||||
are added to the((("transactions", "inputs", "outpoint field", startref="transaction-input-outpoint")))((("inputs", "outpoint field", startref="input-transaction-outpoint")))((("outpoint field (transaction inputs)", startref="outpoint"))) database.
|
||||
|
||||
[[internal_and_display_order]]
|
||||
.Internal and Display Byte Orders
|
||||
|
Loading…
Reference in New Issue
Block a user