Also remove STANDARD_CHECKDATASIG_VERIFY_FLAGS.
deadalnix Fabien markblundeberg jasonbcox
- Group Reviewers
- Maniphest Tasks
- T653: Clean up past upgrades
- rSTAGINGb2d3f35dac10: Add CHECKDATASIG to standard flags.
rABCb2d3f35dac10: Add CHECKDATASIG to standard flags.
Also did make check with test change only, and with code change only,
to check that it fails as expected.
Did IBD on mainnet and testnet with -checkpoints=0 -assumevalid=0
Depends on D3063
|23 ↗||(On Diff #8729)|
I changed the test to subtract SCRIPT_ENABLE_CHECKDATASIG from flags during the tests, rather than adding it. So it ends up passing the same flags values into the test (assuming SCRIPT_ENABLE_CHECKDATASIG is included in STANDARD_SCRIPT_VERIFY_FLAGS and MANDATORY_SCRIPT_VERIFY_FLAGS).
If we want CHECKDATASIG in STANDARD_SCRIPT_VERIFY_FLAGS only, and not in MANDATORY_SCRIPT_VERIFY_FLAGS, then I will have to re-jig the test in some other way.
A few changes, but overall, it looks good.
It's probably better to do & ~SCRIPT_ENABLE_CHECKDATASIG
But more appropriately, just leave it standard and do the setting/clearing in the test.
This expect the flag to be present, so it sets it.
This expects the flag to be absent, which happens to work due to the test cases provided, but this is actually where the problem is.
This test should not assume anything particular about the input that it is given - or, if so, it should check for it in a design by contract fashion ( https://en.wikipedia.org/wiki/Design_by_contract )
Keep the datasigflags name.