mirror of
https://github.com/logos-messaging/docs.waku.org.git
synced 2026-01-07 07:13:12 +00:00
0cb2be1c35
* 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
26 lines
741 B
Markdown
26 lines
741 B
Markdown
---
|
|
title: Static Peers
|
|
hide_table_of_contents: true
|
|
displayed_sidebar: 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](/run-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
|
|
|
|
```mdx-code-block
|
|
import StaticPeers from "@site/diagrams/_static-peers.md";
|
|
|
|
<StaticPeers />
|
|
``` |