arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-02-16 17:42:06 +00:00
Code Issues Releases Wiki Activity

Edited ch06_transactions.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-19 00:45:23 +00:00
parent 8da3c29ce9
commit fc34a11d37
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ch06_transactions.adoc
View File

@ -282,7 +282,7 @@ This txid is in Bitcoin's internal byte order for hashes; see
<<internal_and_display_order>>. <<internal_and_display_order>>.
Because transactions may contain multiple outputs, Alice also needs to 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 its _output index_. Output indexes are 4-byte unsigned
integers starting from zero. 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 - Proof that the previous output exists in the blockchain (or as a known
unconfirmed transaction) and that no other transaction has spent it. unconfirmed transaction) and that no other transaction has spent it.
One of Bitcoin's consensus rules forbids any output from being spent 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 _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 both Bob and Carol in separate transactions. Two transactions that each try to spend the
same previous output are called _conflicting transactions_ because same previous output are called _conflicting transactions_ because