Part of the Filecoin ProPGF Batch 3 grant (#3602).
Finalize the WebRTC-Direct v2 specification and ship its implementation in js-libp2p, with interoperability validated against go-libp2p.
This one is time-sensitive. WebRTC-Direct v1 depends on ICE credential munging, which Chrome is in the process of removing. Until v2 ships, that is the connectivity path every browser client uses to dial a public node.
go-libp2p merged its implementation on 2026-07-08 and shipped it in v0.49.0 on 2026-07-28, so the counterpart to interoperate against already exists and the wire format is settled in practice.
Completion criteria: WebRTC-Direct v2 specification finalized and a working implementation shipped in js-libp2p, with interoperability validated against go-libp2p.
Target: November 14, 2026.
Work for this milestone should reference this issue so it collects here.
Part of the Filecoin ProPGF Batch 3 grant (#3602).
Finalize the WebRTC-Direct v2 specification and ship its implementation in js-libp2p, with interoperability validated against go-libp2p.
This one is time-sensitive. WebRTC-Direct v1 depends on ICE credential munging, which Chrome is in the process of removing. Until v2 ships, that is the connectivity path every browser client uses to dial a public node.
go-libp2p merged its implementation on 2026-07-08 and shipped it in v0.49.0 on 2026-07-28, so the counterpart to interoperate against already exists and the wire format is settled in practice.
Completion criteria: WebRTC-Direct v2 specification finalized and a working implementation shipped in js-libp2p, with interoperability validated against go-libp2p.
Target: November 14, 2026.
Work for this milestone should reference this issue so it collects here.