You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, node operators must pass their Ethereum private key to their nodes to register with the RLNv2 smart contract. This approach introduces unnecessary security risks and complexity. There is no user-friendly interface for registering memberships, managing RLN credentials, or generating keystores that are compatible with nwaku. Additionally, there is no reliable mechanism for caching or managing keystores locally.
User Story
As a user, I want to register RLNv2 memberships through a web dapp, so that I don’t have to provide my Ethereum private key to my node.
As a user, I want to use my preferred wallet for interacting with the RLNv2 smart contract, so that I can maintain flexibility and convenience.
As a user, I want to automatically generate and download an RLNv2 keystore after registration, so that I can use it with my nwaku node securely.
As a user, I want the web dapp to cache my keystores locally, so that I can easily retrieve them without needing to re-register immediately.
As a user, I want the web dapp to show me a list of my cached keystores and notify me to download them, so that I can ensure they are securely stored outside the browser.
As a user, I want the web dapp to show me information about keystores that are cached on the web page, so that I can see what limits and other information is attached to it.
As a user, I want the web dapp to allow me to upload keysotres from file, so that I can see what limits and other information is attached to them.
Description
Currently, node operators must pass their Ethereum private key to their nodes to register with the RLNv2 smart contract. This approach introduces unnecessary security risks and complexity. There is no user-friendly interface for registering memberships, managing RLN credentials, or generating keystores that are compatible with nwaku. Additionally, there is no reliable mechanism for caching or managing keystores locally.
User Story
Proposed Solution / Feature Design
Preliminary breakdown
js-rln
code tojs-waku
Move this to js-waku monorepo js-rln#69rln.waku.org
: Jenkins;nwaku-compose
- questionable;Optional: Diagram or Draft of Design
TBD
Notes
The text was updated successfully, but these errors were encountered: