E01-I2: Yes
Rationale
The public I2P Python README reports successful NTCP2 handshake interoperability against live Java I2P 2.x peers. It identifies bimo.studio as the author and describes a from-scratch Python implementation, not a binding or wrapper of the Java router; it expressly states that Java project code was not copied. This is a public implementer report of exchanged NTCP2 handshake traffic between independent code lineages. Credit this selected router-to-router transport function, consistent with E01 allowing explicitly bounded tested functions.
Assessment method
Public implementer-report review with explicitly limited function credit; no new interoperability execution
Source context
Public implementer README and 0.1.0 changelog dated 2026-03-23; Python NTCP2 source; retained commit 65a1e8dc0791e861d9277a2039e1c2e71345e4bd and hashes
Outstanding qualification
Implementer-reported result, not independently repeated here. The retained repository revision identifies the report, not the exact Python build used in the test; the Java peer version is given only as 2.x. No packet capture, exact test date, peer inventory or detailed test log is supplied in the README. Credit only NTCP2 handshake exchange, not end-to-end application delivery, tunnel construction, multiple active outbound tunnels, private bootstrap, all-IPv4 deployment, memory-only history policy, current PQ extensions or the complete selected configuration. No E04 reproducibility, security, performance or six-month operation claim follows. The broad README claim of a complete router is not adopted as a separate implementation qualification.
Public sources
- https://tangled.org/distributed.camp/i2p-python/blob/main/README.md
- https://tangled.org/distributed.camp/i2p-python
- https://i2p.net/en/docs/specs/ntcp2/
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round335-sources.json