feat: allow subscribeToContentTopic to use other cluster IDs

waku-org / js-waku

JavaScript implementation of Waku v2

https://js.waku.org

Apache License 2.0

166 stars 42 forks source link

feat: allow subscribeToContentTopic to use other cluster IDs #1900

Open fbarbu15 opened 5 months ago

fbarbu15 commented 5 months ago

This is a change request

Problem

subscribeToContentTopic starts a new node with partial ContentTopicInfo (no clusterId) so createLightNode will resolve clusterId to DEFAULT_CLUSTER_ID=1 But Autosharding will be possible on other cluster IDs as well with https://github.com/waku-org/nwaku/issues/2502

Proposed Solutions

Allow clusterId as a parameter in subscribeToContentTopic

chair28980 commented 5 months ago

Blocked by https://github.com/waku-org/nwaku/issues/2502

fbarbu15 commented 5 months ago

This was fixed on nwaku side here

weboko commented 4 months ago

Moving to the top of Todo column to be taken next once release related and reliability bugs are done.