Pierre Krieger

Closing. We need a proper checkpoint format before implement that. cc https://github.com/paritytech/substrate/issues/11184

`wasm32-unknown-unknown` has a `std`, so this is off topic. But yes, the `smoldot` and `smoldot-light-base` libraries compile for Wasm, that is checked by CI.

cc https://github.com/libp2p/specs/issues/220

As a small note, WebRTC is unfortunately not available from within JS workers (despite WebSockets being available, don't ask me), so we would have to do some messages exchanges between...

Considering that we might need to add another encryption layer within the DTLS+SCTP stream, it makes sense to me to simply open one SCTP channel for everything and apply Noise+Yamux...

WebRTC should solve a problem related to blacklisted IP addresses, which I won't go into details to avoid someone "exploiting" this (though it's not really an exploit, just a way...

After https://github.com/paritytech/smoldot/pull/2352: - [x] Add support for a `/webrtc` (or similar) protocol in `Multiaddr`. - [x] Actually add support for WebRTC in the smoldot JS code (`bindings-smoldot-js.ts`). - [x] Finish...

After https://github.com/paritytech/smoldot/pull/2579, what remains to do is: - [x] https://github.com/paritytech/smoldot/pull/2759 - [ ] Implement the meta-headers in each message. - [ ] Stabilize the whole thing by removing the `enableExperimentalWebRTC`...

Another thing to do is fix compatibility with Firefox. As explained [here](https://github.com/libp2p/specs/pull/412/files#diff-10725e780e3c8583b65c128ab23ebc6b3f5502f68b922e33bd86d941c7d601c3R285-R287), Firefox doesn't support `getFingerprints` and you have to find the fingerprints in the local SDP offer.

Thanks for the report! This is a duplicate of https://github.com/paritytech/smoldot/issues/1433, but we can leave it open.