-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Membership for all internal CCs #53
Comments
All CC's are empowered to use the |
I cannot close this issue, so please do :) |
On top of that this bounty could also help waku-org/bounties#9. Same functionality as rln-keystore-generator but via a UI. |
Closing per @rymnc's comment :) |
To kickstart dogfooding, a membership mechanism mostly focused on getting internal CCs to start using RLN. This could e.g. provide instructions to internal CCs on how to generate, configure and keep a suitable key for RLN, collect public key material for eligible CCs (and other parties) via a Typeform, register a membership on their behalf in a membership contract and ensure that deployed nodes are aware of this contract. At this stage the membership contract can still be deployed on a testnet, although we may want to migrate these initial members to a "final" mainnet contract once stable.
Priority: Critical for launch
The text was updated successfully, but these errors were encountered: