G02-I2: Yes
Rationale
A destination retains its identity while its router changes NTCP2 attachment, rebuilds inbound tunnels and publishes their gateways and tunnel IDs in a new LeaseSet. RouterInfo carries changed transport contacts. Publication targets selected floodfills and the responsible routing-key neighborhood; forwarded replicas with a zero reply token do not reflood. Interested peers retrieve updated records. Reachability information changes outside the access region without requiring every participant to receive each destination's attachment update.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
I2P netDb distribution and pinned Java tunnel/transport sources
Outstanding qualification
Use the existing C01 witness with preserved destination keys, reachable peers and successful replacement tunnels on already-routed access prefixes. Responsible directory participants need not be geographically local. Replica rotation, verification, retries and peer lookups add recipients and traffic; this is not a fixed total-cost bound. Stale records and isolation can delay recovery. Existing streams need not survive. No global-scale benchmark, instant convergence, MetaLeaseSet or i2pd post-quantum implementation qualification is inferred.
Public sources
- https://www.i2p.net/en/docs/overview/network-database/
- https://github.com/i2p/i2p.i2p/blob/37039e6594f1372368f0c1cf8258cdaf805a7fb4/router/java/src/net/i2p/router/tunnel/pool/TunnelPool.java
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round555.html
- round555-sources.json