Repository navigation
Add QUIC support in js-libp2p — Libp2p/2025 #34
Description
Activity
- added a parent issue
on May 2, 2025 The Node.js core devs are targeting the 25.0.0 release to include QUIC natively. This is a much better solution than using the Rust implementation as per
@chainsafe/js-libp2p-quic.There is no release issue to track Node.js 25.0.0 yet but one may appear in https://github.com/nodejs/Release closer to the date.
The subsequent actions for this piece of work are to engauge with the Node.js core dev(s) and ensure that the QUIC API that is settled on meets our requirements.
Given https://ipshipyard.com/blog/2025-libp2p-maintenance-update/ it's not clear to me if Shipyard will be landing this piece of work.
Metadata
Metadata
Assignees
Type
Projects
- Status
Add QUIC support in js-libp2p
Add support for the QUIC transport in node js-libp2p. This is crucial for Ethereum consensus client interoperability and future plans.
Timeline
Q2-Q3 2025
Key users
Expected impact & success criteria
This has a great impact on the Ethereum beacon chain. Ethereum consensus clients want to shift to use QUIC as their primary transport away from TCP. Adding support for QUIC in js-libp2p is critical for this effort in order to bring Lodestar to parity.
Additionally, Eth consensus clients also want to deprecate mplex and because yamux isn’t implemented or well tested in many libp2p implementations, the Consensus clients favor moving to QUIC outright.
Another area of impact is help with NAT hole punching for js-libp2p in Node.js which has higher success rates with QUIC over TCP.