Skip to content
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

feat (rln-relay): allow higher messaging rate using multiple valid registrations #1264

Closed
2 tasks
staheri14 opened this issue Oct 13, 2022 · 2 comments
Closed
2 tasks

Comments

@staheri14
Copy link
Contributor

Problem

Waku-rln-relay protocol only accepts one valid rln credential for messaging in a given group. However, it is perceivable that a node wants to increase its messaging quota by using multiple valid credentials. This issue is to enable such a feature in the waku-rln-relay protocol.

Suggested solution

At a high level, the waku node should be able to accept multiple valid rln credentials and use them in a cyclic fashion so that the user benefits from his maximum messaging quota.

Additional context

Was raised in #1238 (comment)

Acceptance criteria

  • A proper solution is devised and implemented in nim-waku
  • the RFC gets updated as fits
@staheri14 staheri14 added the track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications label Oct 13, 2022
@staheri14 staheri14 moved this to New in Vac Research Oct 14, 2022
@staheri14 staheri14 moved this from New to Later/Icebox in Vac Research Oct 14, 2022
@jm-clius jm-clius removed this from Waku Nov 16, 2022
@rymnc rymnc added track:rlnp2p and removed track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications labels Jan 19, 2023
@rymnc
Copy link
Contributor

rymnc commented Feb 28, 2023

https://github.com/Rate-Limiting-Nullifier/rln-circuits-v2 allows this. This issue is blocked by -

  • contract implementation required
  • zerokit implementation required

@chair28980
Copy link
Contributor

Closing per nwaku pm meeting Sep 12 '23. Can reopen if this becomes a requirement. @rymnc

@github-project-automation github-project-automation bot moved this from Later/Icebox to Done in Vac Research Sep 12, 2023
@github-project-automation github-project-automation bot moved this to Done in Waku Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

4 participants