Prithvi Shahi

Ideally this is something the cpp-libp2p maintainers can take on and not the PL libp2p or docs team

ref: https://github.com/libp2p/go-libp2p/issues/2294

Ideally this is something the nim-libp2p maintainers can take on and not the PL libp2p or docs team

@Menduist thanks, in this case, perhaps we can just create a page that links or redirects to your website. This way, we get the benefit of having a nim tutorial...

Two of the 3 places where multistream is used will be changed. See: - https://github.com/libp2p/specs/issues/426 - https://github.com/libp2p/specs/pull/353 And multistream will only remain for protocol negotiation (until it is also replaced...

go-libp2p v0.23.3 has been released https://github.com/libp2p/go-libp2p/releases/tag/v0.23.3 which incorporates @thibmeu 's fix for the missing HTTP Host header in `/wss`

cc @Jorropo @guillaumemichel

Does the option exist for devp2p to move off of RLPx and utilizes libp2p's WebTransport or WebRTC (for browser-to-server and browser-to-browser connectivity)?

@fjl is there any interest in your part (or in the devp2p community) to utilize libp2p and its transports? Would be happy to re-engage on this and help from the...

@fjl glad to hear that. Is it possible to enable all transports to begin with? libp2p will select the best transport to use when dialing a peer. If you only...