Roland Urbano 3f573ef293 fix(config): error on ambiguous peer ID prefix (#113) ... FindPeerByIDPrefix previously returned the first peer whose ID started with the given prefix, silently ignoring further matches. With Ed25519 peer IDs all sharing the leading "12D3KooW" (8 chars), short prefixes can match multiple peers; the chosen peer then depends on slice order, which is effectively undefined from the user's perspective. Change FindPeerByIDPrefix and its wrapper FindPeerByCLIRef to return (*Peer, error): - 0 matches -> (nil, nil) - 1 match -> (&peer, nil) - 2+ match -> (nil, error) describing the ambiguity Call sites in config.Read and rpc/server.go updated accordingly: ambiguity surfaces as a config-load / CLI error instead of a silent wrong-peer resolution. Not a wire-protocol or config-format change. Only behavior visible at CLI invocation and config load. Users relying on short prefixes that happened to match multiple peers will now see a clear error and must lengthen the prefix.		2026-05-23 22:26:05 +02:00
..
config.go	fix(config): error on ambiguous peer ID prefix (#113)	2026-05-23 22:26:05 +02:00
idhash.go	Service Network (#15)	2024-05-14 17:14:42 +02:00