Waku v2 Websocket support

[D4nte]

Problem

Currently, libp2p only supports websockets and webrtc in the browser. We decided to start with websockets.

As nim-waku is the intended waku full node, browser client needs a way to connect to nim-waku nodes.

Additionally, as described in waku-org/js-waku#50, the websocket connections needs to be wrapped in TLS. As modern browsers simply block insecure websocket connection within an https page.

My understanding is that the intent of nim-waku is to be ran by the community to run a network. Thus, it should be consider how one can easily deployed nim-waku with wss enabled (certificate generation, etc).

Acceptance criteria

• Ensure nim-waku can be run with Websockets and connect with js-waku
• Ensure this works with wss enabled
• Deploy and test with test fleet
• Relevant spec changes as a new capability for Waku (10/WAKU2: Define supported transports in spec vacp2p/rfc#458)
• Add a basic tutorial to docs folder explaining how to setup a node with wss enabled (e.g. a couple of openssl command lines to generate an ip certificate).

References

• nim websockets library: Rework status-im/nim-websock#5
• nim-libp2p websockets support: Websockets support vacp2p/nim-libp2p#407

[jm-clius]

I might be missing something, but it doesn't look like this is integrated in nim-libp2p yet?

Tracking issue there: vacp2p/nim-libp2p#407

[jm-clius]

blocked-by vacp2p/nim-libp2p#407

[D4nte]

Sorry about that, I jumped the gun!

[jm-clius]

Unassigning myself here for now to clean up some issues. Feel free to ping me once this is unblocked/becomes a priority.

[D4nte]

Please note I updated the description to include wss.

[D4nte]

nim-libp2p is ready: vacp2p/nim-libp2p#407 (comment).

[oskarth]

Probably good for a new hire

[oskarth]

@rshiv I think OP still has some open items for this to be closed.

Feel free to break out individual items into their own issues - in general the more granular (while still being useful on its own) the better

[rshiv]

All the task related to web-sockets is achieved including test in the fleets.
However, I want to mention an issue in websock which might cause the fleets to go unpredictable and crash for websocket address, status-im/nim-websock#79.

@D4nte Please review the changes and feel free to close the issue.

[D4nte]

Awesome news. Yes, will review, tracking with waku-org/js-waku#327.
Will open new issues if I encounter any bug.