summaryrefslogtreecommitdiff
path: root/bip-0119/fifty.png
diff options
context:
space:
mode:
authorDr. Maxim Orlovsky <orlovsky@pandoracore.com>2021-11-07 09:45:01 +0100
committerDr Maxim Orlovsky <orlovsky@pandoracore.com>2021-11-08 22:07:28 +0100
commit592cb6fa0c8e1484488cfc4e43fe1e4825c17132 (patch)
treeaf0e6253e3e90f3c2b8ca5a03a40c3bdbee5a881 /bip-0119/fifty.png
parentf0cb046b116e3c05814eeb6dc48180b96fa16613 (diff)
downloadbips-592cb6fa0c8e1484488cfc4e43fe1e4825c17132.tar.xz
BIP-341: allow future softforks for leaf version signature verification
Currently the BIP-341 and BIP-342 leave the question of how to verify signature for non-`0xC0` leaf version scripts undefined. I haven't checked the Bitcoin Core code for that matter yet, but (1) I think we need to cover signature validation of non-`0xC0` leaf version scripts in this standard and (2) the only way of doing that is "always succeed" rule for the future leaf version values (otherwise we will need a hard fork to introduce them).
Diffstat (limited to 'bip-0119/fifty.png')
0 files changed, 0 insertions, 0 deletions