mirror of
https://github.com/bitcoin/bips.git
synced 2025-02-26 08:59:43 +01:00
Merge pull request #85 from sipa/201910_c1
Small fix: 0xc1 is possible as first control block byte
This commit is contained in:
commit
c8e82957a2
1 changed files with 1 additions and 1 deletions
|
@ -47,7 +47,7 @@ The rules below only apply when validating a transaction input for which all of
|
|||
* The transaction output is a '''segregated witness spend''' (i.e., the scriptPubKey is a witness program as defined in BIP141).
|
||||
* It is a '''taproot spend''' as defined in bip-taproot (i.e., the witness version is 1, the witness program is 32 bytes, and it is not P2SH wrapped).
|
||||
* It is a '''script path spend''' as defined in bip-taproot (i.e., after removing the optional annex from the witness stack, two or more stack elements remain).
|
||||
* The leaf version is ''0xc0'' (i.e. the first byte of the last witness element after removing the optional annex is ''0xc0'')<ref>'''How is the ''0xc0'' constant chosen?''' Following the guidelines in bip-taproot, by choosing a value having the two top bits set, tapscript spends are identifiable even without access to the UTXO being spent.</ref>, marking it as a '''tapscript spend'''.
|
||||
* The leaf version is ''0xc0'' (i.e. the first byte of the last witness element after removing the optional annex is ''0xc0'' or ''0xc1'')<ref>'''How is the ''0xc0'' constant chosen?''' Following the guidelines in bip-taproot, by choosing a value having the two top bits set, tapscript spends are identifiable even without access to the UTXO being spent.</ref>, marking it as a '''tapscript spend'''.
|
||||
|
||||
Validation of such inputs must be equivalent to performing the following steps in the specified order.
|
||||
# If the input is invalid due to BIP16, BIP141, or bip-taproot, fail.
|
||||
|
|
Loading…
Add table
Reference in a new issue