From 8da3c29ce90823c98b33a1c0d614c89bcaba553d Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 00:43:11 +0000 Subject: [PATCH] Edited ch06_transactions.adoc with Atlas code editor --- ch06_transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index 56effd0a..6b798055 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -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