[Epic] Run waku workshop internally

[alrevuelta]

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. [BOUNTY] Develop a front-end for waku nodes bounties#9 or something developed internally. [Epic] 4.1: Basic front end for node operator #100
• Bootstrap node cc @SionoiS (cant find the issue in infra)

cc @jm-clius @fryorcraken

[fryorcraken]

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

[SionoiS]

Once waku-org/nwaku#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.