1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-26 09:58:22 +00:00

Edited ch06_transactions.adoc with Atlas code editor

This commit is contained in:
clenser 2023-10-19 00:28:02 +00:00
parent b0c243d0cb
commit 07eeee70b5

View File

@ -89,7 +89,7 @@ image::images/mbc3_0601.png["A byte map of Alice's transaction"]
[[version]] [[version]]
=== Version === Version
The first four bytes of a serialized Bitcoin transaction are its The first ((("transactions", "version of", id="transactions-version")))((("version (of transactions)", id="version-transactions")))four bytes of a serialized Bitcoin transaction are its
version. The original version of Bitcoin transactions was version 1 version. The original version of Bitcoin transactions was version 1
(0x01000000). All transactions in Bitcoin must follow (0x01000000). All transactions in Bitcoin must follow
the rules of version 1 transactions, with many of those rules being the rules of version 1 transactions, with many of those rules being
@ -144,7 +144,7 @@ being widely considered. That proposal does not seek to change the
consensus rules but only the policy that Bitcoin full nodes use to relay consensus rules but only the policy that Bitcoin full nodes use to relay
transactions. Under the proposal, version 3 transactions would be transactions. Under the proposal, version 3 transactions would be
subject to additional constraints in order to prevent certain Denial of subject to additional constraints in order to prevent certain Denial of
Service (DoS) attacks that we'll discuss further in <<transaction_pinning>>. Service (DoS) attacks that we'll discuss((("transactions", "version of", startref="transactions-version")))((("version (of transactions)", startref="version-transactions"))) further in <<transaction_pinning>>.
=== Extended Marker and Flag === Extended Marker and Flag