Gasless L2 track
We’ve previously merged the rln-prover to the Status L2 monorepo to support gasless L2 operations, based on Karma balance.
Within this track, the AnonComms team performs work as a service unit in aid of Status Network’s requirements. However, the work here will have wider value for the Logos ecosystem, not least in making RLN more flexible to allow burning multiple message IDs in a single proof, deploying a separate RLN prover module, and proving the application of RLN for fair-use gasless transactions.
Within this track, we’ll also enable multiple provers to operate on a shared database, extend RLN (and Zerokit) to support burning multiple IDs in a single proof, and implement a multi-slasher topology. All of this is published in a specification, culminating in a whitepaper and academic paper describing the RLN prover approach to gasless L2 transactions.
Roadmap
FURPS: Zerokit FURPS
Scheduled milestones:
Risks
| Risk | (Accept, Own, Mitigation) |
|---|---|
| Dependency on the Status L2 team for adaptation-related improvements | Collaboration with the Status L2 team through codebase and document reviews |
Deliverables
Allow multiple RLN provers to share a database
Owner: AnonComms Zerokit-RLN
Feature: Zerokit-RLN FURPS
FURPS:
- F1. The RLN prover module supports gasless L2 operations
- F2. Multiple RLN prover instances can operate on a shared database
- U4. The RLN prover module has an associated specification
- R1. Multiple RLN prover instances operate consistently without database conflicts
Checklist:
- Specs: link to specs and/or API definition
- Code: link to GitHub issues/PRs/Epic
- Dogfood: link to dogfooding session/artefact
- Docs: links to README.md or other docs
Write whitepaper on gasless L2 transactions
Owner: AnonComms Zerokit-RLN
Feature: Zerokit-RLN FURPS
FURPS:
- S1. A gasless L2 whitepaper is written to document the design and trade-offs
Checklist:
- Docs: link to whitepaper