Add Address Manager spec - #738
Open
gmelodie wants to merge 1 commit into
Open
Conversation
gmelodie
force-pushed
the
feat/addr-manager
branch
5 times, most recently
from
September 1, 2026 19:04
0ea9618 to
05599e4
Compare
gmelodie
force-pushed
the
feat/addr-manager
branch
from
September 1, 2026 19:10
05599e4 to
f2ed58a
Compare
gmelodie
marked this pull request as ready for review
September 1, 2026 19:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A libp2p node learns its own addresses from several sources: the listen addresses that it binds, a port mapping, a relay reservation, an Identify observation, and the configuration of the host operator. No source alone proves that a remote peer can dial the address. Today each source lives in its own component, each one rewrites the announce list, and the answers of AutoNAT per address collapse into one flag.
This spec describes an Address Manager: one component at host level that owns the announce path, separates always-on address discovery from optional reachability confirmation, and delegates confirmation to a replaceable Verifier backed by AutoNAT v2. It defines no message and no wire format, thus a node that adopts it stays compatible with a node that does not.
Unverified,Confirmed,Unreachable).IdentifyandAutonatboth carry an IP that a remote peer chose, and a candidate with only such sources stays unannounced until a verifier confirms it.minCountcounts distinct peers. One peer that reconnects thus cannot choose the external address.OKonly when the AutoNAT v2 dial-back nonce arrived on the address under test, and an announced public address needs two peers before it becomesUnreachable.