Details
- Reviewers
jasonbcox schancel - Group Reviewers
Restricted Project - Commits
- rSTAGING13eb8667a807: Add activation code for OP_CHECKDATASIG
rABC13eb8667a807: Add activation code for OP_CHECKDATASIG
Added an integration test to check for proper activation and deactivation.
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- checksigactivation
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 3023 Build 4139: Bitcoin ABC Buildbot (legacy) Build 4138: arc lint + arc unit
Event Timeline
src/validation.cpp | ||
---|---|---|
1928 | acceptign -> accepting | |
2584 | transactiosn -> transactions | |
test/functional/abc-checkdatasig-activation.py | ||
76 | OP_AND should be OP_CHECKDATASIG. very confusing otherwise. | |
87 | spendable_ands -> spendable_checkdatasigs | |
101 | opreturn -> something about checkdatasig | |
139 | I'm confused how this magic number 6 was selected. With MTP being the last 11 blocks, does selecting fewer potentially make the test flaky and/or fragile to future changes, as there could be blocks mined before these 6 with unknown timestamps? | |
146 | good check. I didn't think about testing the RPC in conjunction with the block acceptance. @schancel we should be on the lookout for stuff like this. in the future, a solid testing framework would be able to make checks like this for us. |
test/functional/abc-checkdatasig-activation.py | ||
---|---|---|
139 | You're referring to the MAGNETIC_ANOMALY_START_TIME value, but I'm talking about MTP calculated using 11 blocks' worth of timestamps, not 6. |
test/functional/abc-checkdatasig-activation.py | ||
---|---|---|
139 | You need to pour in 6 new timestamp for the median to budge. I don't see what's the problem here. |