mirror of
https://github.com/logos-messaging/docs.waku.org.git
synced 2026-01-03 13:23:06 +00:00
20 lines
1.4 KiB
Markdown
20 lines
1.4 KiB
Markdown
---
|
|
title: Peer Discovery
|
|
hide_table_of_contents: true
|
|
displayed_sidebar: learn
|
|
---
|
|
|
|
When initialising a Waku node, it must connect with other peers to enable message sending, receiving, and retrieval. To achieve this, a discovery mechanism is employed to locate other peers in the network. This process is known as bootstrapping.
|
|
|
|
Once a connection is established, the node must actively seek out additional peers to have:
|
|
|
|
- Sufficient peers in the [Relay](/learn/concepts/protocols#relay) mesh: The goal is to have at least 6 peers in the mesh. This ensures a robust network where messages can be efficiently relayed.
|
|
- Reserve peers for backup: It is essential to have a surplus of peers available as reserves. These reserves are backups when the current peers become overloaded or experience unexpected disconnections.
|
|
- Peers with specific capabilities: The node seeks out peers with specific capabilities, such as [Store](/learn/concepts/protocols#store), [Light Push](/learn/concepts/protocols#light-push), or [Filter](/learn/concepts/protocols#filter). This allows for targeted interactions and enhanced functionality based on the desired capabilities.
|
|
|
|
Waku supports multiple peer discovery mechanisms, such as:
|
|
|
|
- [Configuring Static Peers](/learn/concepts/static-peers)
|
|
- [Peer Discovery via DNS](/learn/concepts/dns-discovery)
|
|
- [Discv5 Ambient Peer Discovery](/learn/concepts/discv5)
|
|
- [Peer Exchange](/learn/concepts/peer-exchange) |