mirror of
https://github.com/logos-messaging/pm.git
synced 2026-01-02 14:13:09 +00:00
2d7d683fea
Backporting previous roadmap to help clarity on what is planned and changed in H2. Uses new format https://github.com/waku-org/pm/pull/299
81 lines
3.2 KiB
Markdown
81 lines
3.2 KiB
Markdown
# RLN Mainnet
|
||
|
||
**Estimated date of completion**: 30 June 2025
|
||
|
||
Once complemented, the economical behaviour of RLN will have been specified, implemented and discussed with the Status team. An implementation of RLN for light clients will also be done, to demonstrate RLN’s UX with onchain Merkle tree. Finally, the smart contract will be deployed on mainnet.
|
||
|
||
It will then be possible to design the usage of RLN in Status.
|
||
|
||
|
||
**deliverables**: https://github.com/waku-org/pm/milestone/34
|
||
|
||
## [Implement RLN smart contract for paid, multilevel memberships](https://github.com/waku-org/pm/issues/228)
|
||
|
||
**Owner**: research
|
||
|
||
**Feature**: [RLN Smart Contract](/FURPS/core/rln_smart_contract.md)
|
||
|
||
**FURPS**:
|
||
|
||
- F1. RLN rate limit can be defined in terms of multiple messages per epoch.
|
||
- F2. RLN rate limit is set at membership insertion
|
||
- F3. RLN proof generation and validation only requires Web3 RPC `call`s, no blockchain events or initialisation are needed.
|
||
- F4. An ERC-20 token deposit is needed to insert a membership
|
||
- U1. Application developers can set RLN rate limit at insertion.
|
||
|
||
**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 docs.waku.org (TBD)
|
||
|
||
## [TWN supports RLN onchain tree and deposits, existing memberships only](https://github.com/waku-org/pm/issues/286)
|
||
|
||
**Owner**: nwaku
|
||
|
||
**Feature**: [RLN Smart Contract](/FURPS/core/rln_smart_contract.md)
|
||
|
||
**FURPS**:
|
||
|
||
- F3. RLN initialization only requires Web3 RPC `call`s, no blockchain events are needed.
|
||
- U2. User do not need to wait for merkle tree synchronization and building to start relaying
|
||
or sending messages.
|
||
- P1. New node setup with an RLN membership can be ready to verify RLN proof within 5s,
|
||
no matter the size of the tree **(Vac-DST)**.
|
||
- +1. Smart Contracts are deployed on Linea Testnet.
|
||
- +2. TWN uses smart contracts deployed on Linea Testnet.
|
||
|
||
**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 docs.waku.org (TBD)
|
||
|
||
## [RLNv2 Web management interface](https://github.com/waku-org/pm/issues/281)
|
||
|
||
**Owner**: js-waku
|
||
|
||
**Feature**: [RLN Membership Management](/FURPS/application/rln_membership_management.md)
|
||
|
||
**FURPS**:
|
||
|
||
- F1. Can generate RLN credentials.
|
||
- F2. Can insert RLN membership in smart contract, with accompanying deposit.
|
||
- F3. Can extend RLN membership on smart contract.
|
||
- F4. Can withdraw deposit from smart contract.
|
||
- F5. Membership credentials are encrypted by default on local disk.
|
||
- U1. RLN membership details can be exported and imported.
|
||
- U2. Deployment details (address, chain id) are persisted by library and in exports.
|
||
- R1. Import and exports are interoperable across all implementations.
|
||
- +1. Deployed on https://rln.waku.org
|
||
- +2. Available for Linea Sepolia Testnet contracts.
|
||
- +3. Proof generation and validation is out of scope.
|
||
|
||
For S1. Browser application, using web3 wallet browser extensions.
|
||
|
||
**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 docs.waku.org (TBD)
|