F39-I2: Yes
Rationale
Java I2P ClientManager.distributeMessage looks up the receiving Destination among connected clients. For another local client it invokes DistributeLocal and receiveMessage; otherwise it submits the message to the remote client-message path. Applications keep the Destination reference and I2CP/streaming interface when the peer is local or remote.
Assessment method
Pinned primary implementation: local destination dispatch and remote fallback
Source context
Java I2P 2.6.0 ClientManager.distributeMessage / DistributeLocal; ClientMessagePool.add
Outstanding qualification
Source-level architectural credit for distinct clients sharing one router, not sending to the same client connection, which the code rejects. The local router is trusted with this delivery; local and tunneled cryptographic protection are not asserted equivalent. No runtime test, zero-copy, automatic sharing across isolated routers, or post-quantum qualification follows. Other criterion-specific compositions remain unchanged.
Public sources
- https://github.com/i2p/i2p.i2p/blob/63326dc48b954fcaceae544daa57d9dd9a0c6f4d/router/java/src/net/i2p/router/client/ClientManager.java
- https://github.com/i2p/i2p.i2p/blob/63326dc48b954fcaceae544daa57d9dd9a0c6f4d/router/java/src/net/i2p/router/ClientMessagePool.java
- https://github.com/i2p/i2p.website/blob/main/content/en/docs/api/streaming.md
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round698.html