From fc34a11d373b37d9eb00842c233f60a572ea6edf Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 00:45:23 +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 6b798055..a79f148e 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -282,7 +282,7 @@ This txid is in Bitcoin's internal byte order for hashes; see <>. Because transactions may contain multiple outputs, Alice also needs to -identify which particular output from that transaction to use, called +identify which particular output from that transaction to use, ((("output indexes")))called its _output index_. Output indexes are 4-byte unsigned integers starting from zero. @@ -315,7 +315,7 @@ pieces of information from it: - Proof that the previous output exists in the blockchain (or as a known unconfirmed transaction) and that no other transaction has spent it. One of Bitcoin's consensus rules forbids any output from being spent - more than once within a valid blockchain. This is the rule against + more than once within a valid blockchain. This is the((("double spending")))((("conflicting transactions"))) rule against _double spending_: Alice can't use the same previous output to pay both Bob and Carol in separate transactions. Two transactions that each try to spend the same previous output are called _conflicting transactions_ because