fix broken test
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 23 2019
remove nonbreaking space from comment (U+00A0)
rebase onto fixed feature_cltv.py; const-ify flags
May 22 2019
oops, dropped a comment
address comment: rebase onto D3093
more accurate description; add comments
mini rebase for release notes
Great to see the end of STANDARD_CHECKDATASIG_VERIFY_FLAGS :-)
May 21 2019
Ironically I am having a hard time reproducing the failure mode, now that I actually want to see the before/after change. 🙄
Regarding this: I noticed in a recent reddit discussion that ProHashing does not use accurate timestamps: https://www.reddit.com/r/btc/comments/bqy05r/sensible_defaults_and_unintended_consequences_of/eo9f9fa/
This appears to be getting further along now, but still errors out on my machine.
rebased onto D3082
Oh man, does this explain the build failure I have had on D3076?? It was so confusing...
incorporate small follow-up PR12860 too
Given how STANDARD_SCRIPT_VERIFY_FLAGS appears in some important places, please add IBD to the test plan. :-)
Very confusing build failure ... will return at a later date.
May 20 2019
rebased (still WIP)
I'm happy with this general direction. Given the severity of consequences of not including it in standardness, the checkdatasig_inclusion_in_standard_and_mandatory_flags is nice to have as a fool-proof check. :)
accidental git dependency
In D3014#72496, @deadalnix wrote:The test place doesn't cover RPC tests, however, this is clearly changing RPC tests.
In D3021#72499, @deadalnix wrote:It seems like this would depend on whatever added the get_difficulty_for_null_tip test.
still approve :D
braces