libp2p / libp2p/rust-libp2p

WebTransport protocol for the relay server

Open
#6,149 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
5.6k
Forks
1.3k
Avg merge
8h 47m
Merged PRs (30d)
19

Description

Description

Currently working with wasm p2p web clients along with native relay server if you want to work with webtransport on the wasm and on native relay it wont work, As the crate currently just support the browser end

Motivation

having websocket and webtransport allows much flexibility

Requirements
  1. Wasm to relay communication
Open questions

No response

Are you planning to do it yourself in a pull request?

Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing browser-side WebTransport support and the native relay server entry points. Define the wasm-to-relay communication path and verify that both WebSocket and WebTransport are supported end to end; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.