C01-LP: Yes
Rationale
A libp2p peer can preserve its Peer ID when its old IPv4/QUIC attachment becomes unavailable. A bounded witness advertises a second reachable numeric QUIC listen address through Identify Push while connectivity still exists. The remote peer stores that locator under the same authenticated Peer ID and can dial it after the first attachment fails. go-libp2p v0.50.0 consumes Identify addresses into the peerstore and obtains candidate dial addresses by Peer ID.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
libp2p native peerstore and address updates; BP/SABR over configured LTP contacts
Outstanding qualification
The stable destination is the Peer ID, not the full transport multiaddress. The alternative must be listening, permitted by ConnectionGater, accepted by address filters and learned before losing the only communication path; it must remain in the peerstore until redial. Native Identify exchange is used, with no DHT, DNS, relay service or application redirection added. If no usable locator is known, the dialer returns an address error: arbitrary movement after total disconnection is not credited. A fresh authenticated QUIC connection and new streams are allowed. Unlike QUIC connection-ID continuity alone, this witness includes a native peer-identity-to-locator repository and address-update mechanism. No runtime mobility or universal implementation claim.
Public sources
- https://raw.githubusercontent.com/libp2p/specs/master/identify/README.md
- https://github.com/libp2p/go-libp2p/blob/v0.50.0/p2p/protocol/identify/id.go
- https://github.com/libp2p/go-libp2p/blob/v0.50.0/p2p/net/swarm/swarm_dial.go
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round535.html
- round535-sources.json