[Milestone] Peer management strategy for relay and light nodes are defined and implemented

[fryorcraken]

2023 Milestones: https://notes.status.im/s/iylE6wdli#

Milestone label: E:2023-peer-mgmt
Priority Tracks: Production Readiness
Due date: 31 Aug 2023

Summary

1. suitable discovery methods to find new peers
2. some mechanism to score peers/be biased towards more reliable connections
3. connection management to establish, maintain and re-establish a large, healthy set of connections to peer decisions re peer persistence
4. strategies and measurements around peer connectivity restrictions (e.g. NAT traversal, uni- vs bidirectionality of connections, etc.)

Justification

Proper peer and connection management is crucial to ensure reliable message delivery in a Waku network, due to nature of relay. A strong relayer network is the most basic underpinning of any Waku v2 network. All other Waku services builds on the assumption that the underlying message routing works well and is scalable. For example, each peer in the network must be able to establish and maintain at least six good connections to other peers. Read this summary for what would constitute a "good" connection.

Resource-restricted devices, with limited bandwidth or mostly offline need efficient connection management to ensure that reliable connections are set from the moment the app is started or has network access.

Epics

• nwaku: Sharded peer management and discovery
• js-waku: Peer Management: Automated actions upon reconnection
• js-waku: Peer Management: Scoring, Redundancy and Persistence
• js-waku: Peer Management: Connection and Disconnection
• go-waku: Introduce Peer Management

[fryorcraken]

monthly update

Peer management has been implemented in go-waku, dogfooding with Status Desktop is the last step.
Further progress done in js-waku to use several peers at the same times thanks to peer exchange, also roadmap for js-waku has been defined in more details.

[jm-clius]

Close as completed. Remaining work tracked in #67