docs.waku.org/docs/learn/concepts/static-peers.md
fryorcraken 0cb2be1c35
Re-organise the docs to have clear CTAs (#251)
* Split website in 4:

- build
- run node
- learn
- research

* only show pages of section in sidebar

* home button on each sidebar

* index.md for homepages

* Add video tutorials

* delete old getting-started

* rename to "Waku node"

* fix nwaku compose

* add to dict

* script revert research changes

* fix broken links

* move research index content

* move research folder under learn

* move research folder under learn: side bar and buttons

* remove pointless links
2025-10-03 15:54:25 +10:00

741 B

title hide_table_of_contents displayed_sidebar
Static Peers true learn

Waku applications have the flexibility to embed bootstrap node addresses directly into their codebase. Developers can either use static peers operated by Status or run a node.

Pros

  • Low latency.
  • Low resource requirements.

Cons

  • Vulnerable to censorship: Node IPs can be blocked or restricted.
  • Limited scalability: The number of nodes is fixed and cannot easily be expanded.
  • Maintenance challenges: Updating the node list requires modifying the code, which can be cumbersome and involves releasing and deploying.

Overview

import StaticPeers from "@site/diagrams/_static-peers.md";

<StaticPeers />