aboutsummaryrefslogtreecommitdiff
path: root/libbitcoinconsensus.pc.in
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2021-06-17 09:05:48 +0200
committerMarcoFalke <falke.marco@gmail.com>2021-06-17 09:05:52 +0200
commitdd24567a243fd71ab2fe991b431f805bcc3f7b3e (patch)
tree0c6fb1b6b6d43d60e466396197409015be7281fb /libbitcoinconsensus.pc.in
parentd50302625e115da2bd4bcaf14c90c8b0e4872bc7 (diff)
parent754e802274e9373ad7e1dccb710acf74ded6e7fb (diff)
Merge bitcoin/bitcoin#22120: test: p2p_invalid_block: Check that a block rejected due to too-new tim…
754e802274e9373ad7e1dccb710acf74ded6e7fb test: check rejected future block later accepted (Luke Dashjr) Pull request description: (Luke) was unsure if the code sufficiently avoided caching a time-too-new rejection, so wrote this test to check it. It looks like despite only exempting BLOCK_MUTATED, it is still okay because header failures never cache block invalidity. This test will help ensure that if this ever changes, BLOCK_TIME_FUTURE gets excluded at the same time. This PR re-opens https://github.com/bitcoin/bitcoin/pull/17872 which went stale and addresses the nits raised by reviewers there. ACKs for top commit: MarcoFalke: review ACK 754e802274e9373ad7e1dccb710acf74ded6e7fb Tree-SHA512: a2bbc8fffb523cf2831e1ecb05f20868e30106a38cc2e369e4973fa549cca06675a668df16f76c49cc4ce3a22925404255e5c53c4232d63ba1b9fca878509aa0
Diffstat (limited to 'libbitcoinconsensus.pc.in')
0 files changed, 0 insertions, 0 deletions