E04-LP: Yes

Rationale

Kasyanchuk (2026), author of the competing librats implementation, reports external js-libp2p 3.3.8 measurements with hardware, Node version, TCP/Noise configuration, loopback workload, pacing and three-run median method. Quantitative results include memory and transfer behavior. Tong (2023) separately publishes rust-libp2p perf commands and byte/time results for loopback transfers with controlled delay or loss. These measure executed libp2p peer connections and streams. The connection specification establishes the shared reliable, bidirectional stream abstraction across TCP and QUIC transports. Under the revised E04 definition, this is evidence of independent quantitative measurement of a relevant protocol mechanism.

Assessment method

Revised E04 documentary assessment; shared stream mechanism, transport-scoped evidence

Source context

External js-libp2p and rust-libp2p measurements; libp2p connection specification

Outstanding qualification

The measured stacks use TCP, not the selected go-libp2p QUIC/TLS stack. Shared stream semantics justify relevance, not numerical transferability: transport, security, multiplexing, language and implementation costs differ. No QUIC, migration, ConnectionGater or post-quantum performance is inferred. Kasyanchuk has an explicit commercial/competitive interest; his libp2p baseline is external to libp2p, not a neutral ranking. Tong presents an external user experiment; no exhaustive contributor audit is claimed. Small loopback studies do not establish Internet performance, scale or statistical robustness. E04 records availability of published measurements, not favorable performance. No benchmark was rerun.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

round623.html
round623-sources.json