ProofPool has historically been a construct only manipulated by PeerManager.
We can cleanup PeerManager's API by exposing the pools but first we need to
ensure ProofPool's API is also clean and acceptable for use outside of the
context of PeerManager. This means not accidentially altering pools that we
fetch from PeerManager.
Details
Details
- Reviewers
Fabien - Group Reviewers
Restricted Project - Commits
- rABC8d208e1ea83e: [avalanche] Improve const correctness of ProofPool::countProofs()
ninja check
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable