alrevuelta commented 10 months ago

Summary

We currently have cluster-id=1 for TheWakuNetwork and 0xF1935b338321013f11068abCafC548A7B0db732C as the RLN contract, so we can start dogfooding The Waku Network internally.

I would like to suggest:

Run non-technical workshop internally so that Status CCs can learn how to run their own full node and use it to publish messages to different topics.
Note: This focuses on nwaku as a full node, and light clients are out of scope.

Prerequisites:

[ ] Fritctionless UI-friendly rln membership generation. cc @weboko
[ ] Front end with some basic functionality. https://github.com/waku-org/bounties/issues/9 or something developed internally. https://github.com/waku-org/pm/issues/100
[ ] Bootstrap node cc @SionoiS (cant find the issue in infra)

cc @jm-clius @fryorcraken

fryorcraken commented 10 months ago

I would suggest to make that an epic as part of Gen 0 milestone.

SionoiS commented 9 months ago

Once https://github.com/waku-org/nwaku/pull/2151 is merged. It would be cool to run some nodes with only a couple of shards instead of the whole 7 used in TWN.

The easy way would be to;

unsubscribe from all topics.
pick a random content topic (or 2-3) and subscribe.
check connection # for each shard.

waku-org / pm

[Epic] Run waku workshop internally #94

Summary