Skip to content

WebRTC-Direct transport at risk due to Chrome changes (ICE credential munging): alignment and next steps #3499

Open

Description

@johannamoran

Description
Sharing a consolidated update from recent discussions across js-libp2p, py-libp2p and specs to align on implications for go-libp2p.

This needs attention as it impacts core connectivity guarantees for browser and server communication.

Context
Recent threads to review:

Summary of the Problem
The /webrtc-direct transport is at risk due to upcoming changes in Google Chrome.

  • WebRTC-Direct exists primarily to allow:
  1. browser to public libp2p server dialing
  2. without signalling
  3. without CA-signed certificates
  • This relies on ICE credential munging (SDP manipulation)
  • Chrome is introducing a restriction (WebRTC-NoSdpMangleUfrag) that breaks this mechanism

When this change rolls out:

  • Browser to server connectivity via /webrtc-direct may stop working
  • The core reason for this transport’s existence is undermined

Impact

  • Existing assumptions about browser and server direct connectivity may no longer hold
  • /webrtc-direct could degrade or become unusable
  • Affects:
  1. onboarding flows
  2. public node access patterns
  3. browser-based libp2p applications

Priority
High

This is externally driven (Chrome changes) and affects a foundational transport. Delay risks breaking connectivity for browser-based libp2p usage.

Activity

  1. lidel commented on Jun 20, 2026

    @lidel
    Contributor

    WebRTC-Direct v2 (no ICE ufrag munging) is ready across all three repos.
    If it helps, I tested it end to end by hand using below revisions (so when in doubt, know this was the state that worked):

    The end-to-end test I did: a JS v2 dialer in Chrome for Testing 150.0.7871.24 run with --force-fieldtrials=WebRTC-NoSdpMangleUfrag/Enabled/ against the Go v2 server. v1 fails (Chrome rejects the munged ufrag), v2 connects and is Noise-authenticated on both sides.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions