[Epic] 1.4: Sharded peer management and discovery

[chair28980]

Epic label: E:1.4: Sharded peer management and discovery

Summary

This epic tracks work necessary to allow applications to interact with shards in a transparent manner. Relay nodes should preferably be subscribed to the shards carrying the content topic(s) the application is interested in. Where this is not the case, the application should be able to interact with service peers within the shards it's interested in via a peer management scheme. The peer manager should be tracking peers from all public shards or be able to discover such peers on demand.

Acceptance Criteria

Tasks

• nwaku: feat: Peer management with shard as a dimension nwaku#1940
• js-waku: feat: Peer management with shard as a dimension js-waku#1505
• js-waku: feat: Peer discovery with dynamic shards as dimension js-waku#1504
• nwaku: feat: Service peer selection on specific shards nwaku#1941
• go-waku: feat: discovery & peer management for static shards go-waku#727
• go-waku: feat: Service peer selection on specific shards go-waku#680
• go-waku: feat: Peer management with shard as a dimension go-waku#679
• go-waku: feat: Peer discovery with dynamic shards as dimension go-waku#678

[SionoiS]

Ok! Dropping my thoughts here.

Goal:
Keep a healthy mix of peers from different shards and capability support.

Input:
Peer scoring system (unrelated to GossipSub) would take as input the peers from discovery. Each peers has an ENR with shards subscribed to and capabilities.

State:
It maybe be useful to keep the score, I'm not sure yet. Other states should be kept like shard subscriptions and own capabilities.

Output:
This system's output would be decisions about which peer to connect OR disconnect from.

MVP:
Scoring "engine" implemented but no "rule" AKA all peers get the same score.

Future:
Adding bonus/malus to peer score based on "rules".
egg. +10 score for peers that support STORE on a shard I'm subscribed to.

[chair28980]

Deprecate named sharding and update lightpush client issues need to be re prioritized to next year.

• js-waku: feat: Deprecate Named Sharding and Update Lightpush Client API js-waku#1690
• go-waku: feat: Deprecate Named Sharding and Update Lightpush Client API go-waku#842
• nwaku: feat: Deprecate Named Sharding and Update Lightpush Client API nwaku#2163