Igor Sirotin bca1267b39

fix(peermanager): prefer connected peers in selection ...

Filter/lightpush peer selection (Automatic -> SelectRandom, and the
service-slot pubsub path) chose uniformly at random among all peers that
support the protocol+pubsub topic, with no regard for connectedness. A
light node that has learned many peers via discv5/peer-exchange — some of
them stale/unreachable (e.g. torn-down nodes whose ENRs a bootstrap node
still advertised) — would therefore keep picking dead peers, churning on
failed dials and missing messages, even while a perfectly good already-
connected service node (e.g. the static fleet node) was available.

Add preferConnectedPeers: bias selection toward peers we are currently
connected to, falling back to the full candidate set when none are
connected (so behavior is unchanged when there is no connected candidate).

Relates to status-im/status-go#7513.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-09 14:48:36 +03:00

..

cliutils

chore: remove bridging topics feature (#949)

2023-12-09 13:59:35 -04:00

metrics

fix: return error in relay publish if exceeding max-msg-size (#939)

2023-12-01 06:53:28 +05:30

persistence

feat: log error and stacktrace when panic in goroutine (#1225)

2024-09-25 17:15:20 +08:00

tools

chore: switch to Google's Protobuf library

2023-02-16 11:37:59 -04:00

try

feat: Implement logic for publish from node

2021-12-07 14:32:02 +01:00

v2

fix(peermanager): prefer connected peers in selection

2026-06-09 14:48:36 +03:00