S04-I2: Yes
Rationale
I2P distributes origin-signed RouterInfo and LeaseSet records through floodfill routers, whose role is not assigned by a central directory authority. Together with the already selected local RouterInfo bootstrap, known destination keys and private-IP allowLocal configuration, participants can operate routing, floodfill and destination roles under their own administration.
Assessment method
Documentary dependency review; no runtime execution
Source context
Primary protocol and configuration documentation; selected composition
Outstanding qualification
Fresh bootstrap data, enough reachable routers for the selected tunnels and a correct clock remain necessary. This credits the existing independent-deployment profile, not a new substitution for the public Internet case. Full isolated-stack execution and anonymity qualification remain unproven.
Public sources
- https://i2p.net/en/docs/overview/network-database/
- https://i2p.net/en/docs/overview/faq/
- https://github.com/i2p/i2p.i2p/blob/37039e6594f1372368f0c1cf8258cdaf805a7fb4/router/java/src/net/i2p/router/transport/ntcp/NTCPTransport.java
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round251-sources.json