-
Notifications
You must be signed in to change notification settings - Fork 42
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
[Epic: js-waku] Provision RLN for light push clients PoC #2150
Comments
Execution plan Step 1: improve bootstrapping and connection to ethereum Metamask:
RLN Instance:
Example showcasing it PRs: waku-org/js-rln#92, waku-org/examples.waku.org#297 Step 2: improve cred management, verification Keystore
Verification:
PR: waku-org/js-rln#93, waku-org/examples.waku.org#299 Step 3: include into RLN Instance:
Files:
|
Leftovers:
|
This is descoped in favour of deliverable "Provision RLN for light push clients PoC" cc @weboko |
Closing as the only leftover is waku-org/js-rln#76 and can be done separately when in priority again. |
Epic label:
E:js-waku User Pays Own RLN Membership
Summary
Enable developers to build application where the users pays for their own credentials.
Acceptance Criteria
Tasks
Notes
For the sake of developer experience, the API should be simple and easy to use (e.g. in less than 20 lines). This means that the library may need to be opinionated in the way contract events are handled, what web3 library is used (etherjs), etc.
Consideration needs to be made on how to handle that in the js-waku package ecosystem. For example. should this be part of the
@waku/sdk
(I would suggest yes).Notes that waku-org/research#45 is not in the scope of the issue. The intent is to get RLN in the hands of developer, the second priority will be to fix the UX.
The text was updated successfully, but these errors were encountered: