-
Notifications
You must be signed in to change notification settings - Fork 9
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
chore: deprecate import in rln-js #232
Comments
Might make sense to do waku-org/js-rln#48 first so that we can have 2 examples:
|
Actually, being able to export credentials when they are created from a signature would be useful. Currently, you have to pass your private key to nwaku to register in the RLN contract. This is not great as your private is seen clear text by your computer (shell history or config file). Instead, one could be encouraged to use Web app to register in RLN contract, and then export the RLN credentials to use them with nwaku. Cc @rymnc, wdyt? We are attempting 2 things with the examples:
Theses two goals are contradictory. First we should review how we want to use examples for Dev Rel. @fryorcraken to discuss with @hackyguru and @LordGhostX. |
Great idea. Please refer to the waku keystore to generate a valid keystore that can be accepted by nwaku - https://github.com/waku-org/nwaku/tree/master/waku/v2/waku_keystore adapted from nimbus' keystore, should be some code you can reuse |
Tracking here the PoC vs examples discussion: #163 (comment) |
Idea is to remove import field for RLN credentials.
More details - #225 (comment)
The text was updated successfully, but these errors were encountered: