docs(anoncomms): Splitting the Release RLN Prover for gasless L2 transactions into two milestones#353
Open
docs(anoncomms): Splitting the Release RLN Prover for gasless L2 transactions into two milestones#353
Conversation
jm-clius
approved these changes
Feb 6, 2026
Contributor
jm-clius
left a comment
jm-clius
left a comment
There was a problem hiding this comment.
Some comments below, but can be merged when addressed.
| @@ -0,0 +1,58 @@ | |||
| # [Implement multi-burn RLN and slasher module](https://github.com/logos-co/anoncomms-pm/milestone/8) | |||
|
|
|||
| **Estimated date of completion**: 31 February 2026 | |||
Contributor
There was a problem hiding this comment.
I don't think 31 February exists... 😅
Suggested change
| **Estimated date of completion**: 31 February 2026 | |
| **Estimated date of completion**: 28 February 2026 |
| By the end of this milestone, | ||
| the RLN proving stack will support burning multiple message IDs within a single proof, | ||
| and an external RLN slasher module will be implemented with authenticated connections to the prover. | ||
| This enables decentralized slashers to reliably observe proofs and detect spam in gasless environments. |
Contributor
There was a problem hiding this comment.
Does this milestone include the work to develop the slasher module itself? From the deliverables and FURPS it seems like we only have to focus on creating authenticated connection between slashers and provers (i.e. both these modules are assumed to exist)?
| @@ -0,0 +1,58 @@ | |||
| # [Implement multi-burn RLN and slasher module](https://github.com/logos-co/anoncomms-pm/milestone/8) | |||
Contributor
There was a problem hiding this comment.
Since milestones are sort of the top-level view that external stakeholders see about our work, perhaps we can be a bit more descriptive? Something like:
"Extend gasless L2 transactions with multi-burn RLN and decentralized slashing"?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We split "Release RLN Prover for gasless L2 transactions" milestone into two milestones to keep the scope easier to manage and enable faster, more focused delivery.
Not that: one of the new milestones has the identical name with "Release RLN Prover for gasless L2 transactions" milestone to keep existing milestone4.
Only requires having the new milestone in anoncomms pm repo and reducing the existing milestone4 by removing multi-burn ID and whitepaper items. (Done!)