mirror of
https://github.com/logos-messaging/docs.waku.org.git
synced 2026-01-03 13:23:06 +00:00
25 lines
724 B
Markdown
25 lines
724 B
Markdown
---
|
|
title: Static Peers
|
|
hide_table_of_contents: true
|
|
---
|
|
|
|
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-a-waku-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 />
|
|
``` |