docs.waku.org/docs/Concepts/transports-in-waku.md
Danish Arora 397be651dc
chore: refactor ordering/naming of markdown files (#29)
* chore: rename md files and use config ordering

it is unfeasible to track the changes in files labelled as '1.md', '2.md', etc and
way easier when the files are named after their contents.

* fix: hint box render

* fix: markdown links
2022-12-23 16:59:16 +05:30

758 B

title
Transports in Waku

Waku v2 is built in top of libp2p, and like libp2p it strives to be transport agnostic. We define a set of recommended transports in order to achieve a baseline of interoperability between clients.

This section describes these recommended transports:

  • Waku nodes uses TCP to communicate by default. A service node should be using TCP to listen to, and connect to other nodes.
  • For browser environments, secure websocket is used. Service nodes are encouraged to setup a SSL certificate to enable incoming connections from browser and serve them.
  • Other protocols such as WebRTC, WebTransport and QUIC have been studied.