[Epic] Waku Relay Topic Sharding: Static Sharding Implementation

[kaiserd]

This isssue is part of the Status scaling MVP effort and tracks the implementation of the static sharding part of 51/WAKU2-RELAY-SHARDING.

Acceptance Criteria

• extend the ENR to support rshard clusters using the One key per Shard Cluster method (see RFC)
• filtering logic to check if an ENR belongs to a node in a specific shard (i.e. pubsub topic)
• associate peers to pubsub topics based on ENR (peer manager)

Client implementation issues:

• js-waku: Static Sharding js-waku#1310
• nwaku: feat: nwaku static sharding nwaku#1643
• go-waku: [Epic] Waku Relay Topic Sharding: Static Sharding Implementation #15 (comment)

Notes

• the RFC is still in raw state, needs field testing
• updates discussed and announced here will be added to the RFC soon
• update 31/WAKU2-ENR

[fryorcraken]

@richard-ramos is this done for go-waku? I guess so but was not clear what set of PR tracked the work.

[richard-ramos]

It is done in go-waku. The following merged PRs introduced such functionality:

• feat: utils for handling shards in enr go-waku#522
• feat: more utils functions to setup a relay shards field on the enr go-waku#563
• feat(discv5): find peers with predicate go-waku#574
• feat: find discv5 peers with shards go-waku#576
• feat: subscribe to shards with --topic and refactors go-waku#595

[fryorcraken]

Static sharding available in all clients