E01-YG: Pending
Rationale
The public ironwood-rs README at 28b14c3 reports successful end-to-end encrypted traffic exchange between its Rust implementation and the Go reference, naming yggdrasil-go v0.5.13. Inspected Rust routing/session code and Cargo dependencies implement the core in Rust rather than wrapping the Go engine. A separate Yggdrasil-ng README at c9a54f1 also reports interoperability with Go 0.5.x, but is supplementary. This identifies concrete interoperability evidence, but src/core.rs describes itself as a faithful port of the Go network and encrypted packages. Separate executables and a Rust rewrite do not by themselves establish independently developed implementations; code lineage remains to qualify. The v0.5.13 Go manifest pins Ironwood 7017dbc; the retained nine-commit comparison to selected d50055b changes queue handling, dependencies, fuzz tests and optional password authentication. With no group password, the signature preimage stays unchanged and the reviewed session/traffic wire format is retained. This supports applicability of the historical core-function evidence; it is a source-based inference, not a new execution against d50055b.
Assessment method
Documentary interoperability evidence, restricted to the reported encrypted core traffic function
Source context
Public implementer reports, pinned Rust port source and retained Go version comparison
Outstanding qualification
Still Pending: the independence requirement is unresolved. Implementer-reported test, not independently repeated here. The retained Rust commit identifies the report, not the exact tested build; no dated packet capture, complete topology or run log is supplied. The report concerns Ironwood encrypted traffic exchange. TLS 1.3, pinned peer keys, numeric IPv4 deployment, the ordinary IPv6/UDP application path and the complete selected configuration are not established by that report. Rust TLS code and a live-peer test branch are available, but code existence is not proof that those branches were exercised; that live test asserts peering, not payload delivery. Yggdrasil-ng explicitly reports TCP peering. No clean-room provenance, institutional non-affiliation, E04 measurement reproducibility, security audit, performance, production maturity or six-month operation conclusion follows. Shared protocol design and Rust rewrites of a Go design are disclosed; separate runtime implementations alone are insufficient to resolve the independence question.
Public sources
- https://github.com/AlexMelanFromRingo/ironwood-rs/blob/28b14c3f0bdd8614d2a94584de49bf0ec2fd9261/README.md
- https://github.com/AlexMelanFromRingo/ironwood-rs/blob/28b14c3f0bdd8614d2a94584de49bf0ec2fd9261/src/core.rs
- https://github.com/AlexMelanFromRingo/ironwood-rs/blob/28b14c3f0bdd8614d2a94584de49bf0ec2fd9261/tests/two_node.rs
- https://github.com/Revertron/Yggdrasil-ng/blob/c9a54f1587bb133a06072596484c972a336db0d2/README.md
- https://github.com/yggdrasil-network/yggdrasil-go/blob/v0.5.13/go.mod
- https://github.com/Arceliar/ironwood/compare/7017dbc41d8e...d50055b11f5ec5b56ee4e56ba9a75261461821dc
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round341-sources.json
- round341-review.json