Geth 1.17.5 stops random churn from dropping its most useful mempool peers
Serguey Asael Shinder2 min readGo-ethereum has changed how its nodes choose which peers to keep. A post on the Ethereum Research forum on 24 September describes CHAMP - chain-anchored, multi-dimensional peer protection - of which the inclusion-based part has shipped in geth v1.17.5, with a request-latency dimension still in development.
The problem it solves is a side effect of a good practice. Nodes have a limited number of connection slots, and long-running nodes fill theirs and rarely free them, so newcomers find the network closed and the connection graph hardens into something predictable and easier to attack. Clients counter this by periodically dropping random peers. Random dropping, however, is blind to quality: the peer that has reliably delivered transactions that end up on-chain is as likely to be cut as one that has contributed nothing. The mempool feels this most because it sits off-chain, with no consensus about which peer behaved well.
CHAMP keeps the churn and adds protected pools on top. In each pool a small set of "champion" peers is shielded from random dropping, while drops land on the unprotected majority - at least 70% of each pool even with all categories active - so the churn rate does not change. Instead of combining quality into one score, it protects the top slice in each dimension separately: a peer survives if it is valuable on any one axis. Two of the three dimensions are tied to on-chain outcomes, crediting a peer only when transactions it delivered first are included at the head of the chain and later finalised.
What it means
Anchoring peer reputation to on-chain results is the notable design choice. A score based on what peers claim or how chatty they are can be gamed; a score based on whether their transactions were actually included is much harder to fake, because the only way to earn it is to feed the node transactions that land. The authors note the idea dates to early 2025 and the problem applies to any open peer-to-peer network with bounded slots, not just Geth or Ethereum.
For node operators the change is on by default and needs no configuration. The practical effect should be a mempool that stays better connected to the peers that matter, which feeds into how quickly transactions propagate. Other execution clients face the same trade-off between openness and quality, and whether they adopt a similar overlay is the next thing to watch.