logos-co/roadmap
1
0
Fork 0
mirror of https://github.com/logos-co/roadmap.git synced 2025-02-02 11:25:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

add links to deliverables (#135)

Browse Source
This commit is contained in:
chair 2024-10-02 01:00:20 -07:00 committed by GitHub
parent cd3272838a
commit 292d06fe0f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/waku/milestones/2024-rln-mainnet.md
View File

@ -32,7 +32,7 @@ Analyse RLN deployment in the Waku proto-network and evaluate its DoS protection
- Do we need a combination of msg/sec and msg allocation/day rate limiting?
## Deliverable: Implement RLN smart contract for paid, multilevel memberships
## Deliverable: [Implement RLN smart contract for paid, multilevel memberships](https://github.com/waku-org/pm/issues/256)
This deliverable is an output of Maturing RLN variables/parameters revision (staking, contract/chain, token) - roadmap.
@ -44,12 +44,12 @@ Expiry of memberships to prevent hogging
Support for RLN in resource-restricted clients, i.e. lightweight proof generation and validation
The exact set of features is to be defined in a RFC, as output of Maturing RLN variables/parameters revision (staking, contract/chain, token) - roadmap.
## Deliverable: RLN contract revision and audit
## Deliverable: [RLN contract revision and audit](https://github.com/waku-org/pm/issues/257)
Once a minimal set of smart contract features for RLN has been implemented, the contract needs to be thoroughly revised (and possibly audited) by a group of experts before it can be used in production.
The Waku team will rely on Vac/SC to proceed/organise the smart contract review and audit
## Deliverable: Deploy RLN smart contract to a L2 mainnet
## Deliverable: [Deploy RLN smart contract to a L2 mainnet](https://github.com/waku-org/pm/issues/258)
The RLN smart contract should be deployed to a Layer 2 mainnet.
@ -57,7 +57,7 @@ A first step here may be to deploy to a Layer 2 testnet first. However, we could
This deliverable tracks all steps to deployment of a production version of the contract to a L2.
## Deliverable: Public dogfooding RLNaaS web app
## Deliverable: [Public dogfooding RLNaaS web app](https://github.com/waku-org/pm/issues/259)
Second part of original scope of dogfooding web app.
One of the proposed strategies to roll out RLN for Status 1:1 chats is to use RLNaaS where a service node attaches RLN proof for light clients. This would enable a roll out of RLN without impacting UX or UI.