1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-02-22 23:08:01 +01:00

bip-141: witness field wording improvement

When describing the `witness` field, reword "witness data" to "witness
field" as "witness data" refers also to the `marker` and `flag` fields.
This commit is contained in:
志宇 2022-07-14 18:32:04 +08:00
parent b505101a2d
commit ac80e11298
No known key found for this signature in database
GPG key ID: F6345C9837C2BDE8

View file

@ -56,7 +56,7 @@ The <code>marker</code> MUST be a 1-byte zero value: <code>0x00</code>.
The <code>flag</code> MUST be a 1-byte non-zero value. Currently, <code>0x01</code> MUST be used.
The <code>witness</code> is a serialization of all witness data of the transaction. Each txin is associated with a witness field. A witness field starts with a <code>var_int</code> to indicate the number of stack items for the txin. It is followed by stack items, with each item starts with a <code>var_int</code> to indicate the length. Witness data is NOT script.
The <code>witness</code> is a serialization of all witness fields of the transaction. Each txin is associated with a witness field. A witness field starts with a <code>var_int</code> to indicate the number of stack items for the txin. It is followed by stack items, with each item starts with a <code>var_int</code> to indicate the length. Witness data is NOT script.
A non-witness program (defined hereinafter) txin MUST be associated with an empty witness field, represented by a <code>0x00</code>. If all txins are not witness program, a transaction's <code>wtxid</code> is equal to its <code>txid</code>.