The current behavior is to protect the best node from each avalanche peer. This is not ideal in the case the peer has a low score such that the probability of being selected is very low.
Depends on D9858.
Ref T1634.
Details
Details
- Reviewers
deadalnix - Group Reviewers
Restricted Project - Maniphest Tasks
- Restricted Maniphest Task
ninja all check-all
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- avalanche_eviction_peer_score
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 16296 Build 32459: Build Diff build-diff · build-debug · build-clang-tidy · build-without-wallet · build-clang · lint-circular-dependencies Build 32458: arc lint + arc unit
Event Timeline
Comment Actions
I don't think this approach makes sense. Peer score is used to chose the poling frequency, so this metric should show in the node's avalanche score. I think you are trying to optimize something that shouldn't exist here.