G03-I2: Yes
Rationale
I2P distributes RouterInfo and destination LeaseSet records through floodfill peers. Iterative lookups operate with partial knowledge of those peers. Tunnel participants forward using established tunnel state rather than requiring a complete catalog of all final destinations at each hop.
Assessment method
Primary documentation and selected firmware review; no runtime experiment
Source context
Official discovery documentation and pinned forwarding code
Outstanding qualification
The selected fresh bootstrap contacts and known destination keys remain prerequisites. Floodfill replication, local caches, tunnel state and IP underlay routes still consume resources. Lookup timeouts, stale records and unavailable peers can prevent discovery; this does not establish G05 or guaranteed delivery.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round495.html
- round495-sources.json