Author: Peter Todd 2014-10-14 19:45:18
Published on: 2014-10-14T19:45:18+00:00
In a discussion regarding the implementation of BIP 62 on Bitcoin-dev, Pieter Wuille argues that requiring canonical bool testing for all boolean-using opcodes would save a lot of bytes. He suggests that if a script author fails to properly 'bool-ize' every boolean-using path that can have non-minimal encodings, one can always create a nVersion=1 transaction manually to spend the output and prevent loss of funds. However, he also acknowledges an opposing argument that there may not be many use cases where BOOLAND and BOOLOR are applied to unsanitized input from scriptSig. Typically, BOOLAND and BOOLOR are applied to stuff generated within the script itself, which is not a malleability concern.
Updated on: 2023-06-09T03:08:32.359982+00:00