Various method that do not actually connect a block call ConnectBlock. ConnectTip is a much better place.
Details
Details
- Reviewers
markblundeberg - Group Reviewers
Restricted Project - Commits
- rSTAGING0a1944e13d58: Move replay protection mempool management in ConnectTip
rABC0a1944e13d58: Move replay protection mempool management in ConnectTip
make check ./test/functional/test_runner.py
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- mempoolcleaup
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 4908 Build 7879: Bitcoin ABC Buildbot (legacy) Build 7878: arc lint + arc unit
Event Timeline
Comment Actions
Change in the right direction with good tests.
Note that ConnectBlock has the following callsites besides ConnectTip:
- TestBlockValidity, used during mining. Previously it was incorrectly clearing during CreateNewBlock at the activation point, now fixed .
- VerifyDB, used during initialization. Clearing during VerifyDB is benign: the VerifyDB is used during step 4 of init, whereas the mempool is loaded from disk in step 10 (ThreadImport).
So, the other call sites did not rely on the mempool clearing for maintaining consensus correctness, and in fact it was harming CreateNewBlock.
(In principle this doesn't have to happen in ConnectTip which has only one callsite (ActivateBestChainStep). Sometimes the ConnectTip result gets dropped due to invalid blocks happening later on, in which case it wasn't necessary to clear the mempool. Still it's an improvement over the previous. 👍)