This will enforce SCRIPT_VERIFY_NULLDUMMY on all segwit and non-segwit transactions when segwit is activated with BIP9.
As we may need more time to implement LOW_S softfork in a better way (see #8533 (comment)), the alternative plan is to implement only NULLDUMMY softfork in 0.13.1 and leave LOW_S as a policy at this moment.
Implement NULLDUMMY softfork482f852da6
fanquake added the label Consensus on Aug 31, 2016
jl2012
commented at 1:47 AM on September 2, 2016:
contributor
Need a 0.13.1 tag
fanquake added this to the milestone 0.13.1 on Sep 2, 2016
petertodd
commented at 5:46 AM on September 2, 2016:
contributor
Concept ACK
dcousens
commented at 11:55 AM on September 2, 2016:
contributor
concept ACK
btcdrak
commented at 8:40 PM on September 2, 2016:
contributor
Concept ACK
btcdrak
commented at 12:29 PM on September 4, 2016:
contributor
needs backport tag.
fanquake added the label Backport on Sep 4, 2016
fanquake added the label Needs backport on Sep 4, 2016
fanquake removed the label Backport on Sep 4, 2016
I propose that reviewers should explicitly acknowledge that this pull request is a correct implementation of a specified version of BIP147. So they should review the relevant codes, for example, in interpreter.cpp.
This is needed because in #8533 we just focused on the PR, but not the consensus codes being activated. NULLDUMMY should be reasonably simple for everything to do more careful review.
For example, a reviewer may use: utACK482f852, ACK BIP147 3649694
sipa
commented at 12:21 PM on September 6, 2016:
member
This is a metadata mirror of the GitHub repository
bitcoin/bitcoin.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2026-04-14 21:15 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me