Skip to content

Add support for WebRTC-Direct transport in MultiAddress / NetworkProtocol #39

@Arlodotexe

Description

@Arlodotexe

Ran into this while migrating unit tests. Kubo/libp2p added webrtc support as of release 0.30.0. The upside is that this allows Kubo to connect to Helia in the browser! The downside is that we need to update the shipyard libraries to recognize the new codec when decoding a MultiAddress.

image

From the Kubo 0.30.0 release notes:

WebRTC-Direct Transport enabled by default
Kubo now ships with WebRTC Direct listener enabled by default: /udp/4001/webrtc-direct.

WebRTC Direct complements existing /wss (Secure WebSockets) and /webtransport transports. Unlike /wss, which requires a domain name and a CA-issued TLS certificate, WebRTC Direct works with IPs and can be enabled by default on all Kubo nodes.

This will be similar to when we added quic-v1 support in #14

Metadata

Metadata

Assignees

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