arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-12-26 08:28:15 +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:32:56 +00:00
parent 812d15aea0
commit 122171a55a
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

@ -148,7 +148,7 @@ Service (DoS) attacks that we'll discuss((("transactions", "version of", startre
=== Extended Marker and Flag
The next two fields((("transactions", "extended serialization format")))((("extended serialization format"))) of the example serialized transaction were added as
The next two fields((("transactions", "extended serialization format")))((("extended serialization format")))((("BIP144 extended serialization format"))) of the example serialized transaction were added as
part of the segregated witness (segwit) soft fork change to Bitcoin's
consensus rules. The rules were changed according to BIPs 141 and 143,
but the _extended serialization format_ is defined in BIP144.
@ -163,7 +163,7 @@ be present. This is compatible with the original version of Bitcoin's
transaction serialization format, now called _legacy serialization_.
For details, see <<legacy_serialization>>.
In legacy serialization, the marker byte would have been interpreted as
In ((("transactions", "legacy serialization")))((("legacy serialization")))legacy serialization, the marker byte would have been interpreted as
the number of inputs (zero). A transaction can't have zero inputs, so
the marker signals to modern programs that extended serialization is
being used. The flag field provides a similar signal and also