From 17fa3fe6873ed3236917f7b2adb9b4a5e0668cfd Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Wed, 4 Jun 2025 14:22:42 +1000 Subject: [PATCH] Feedback re RLN --- FURPS/core/incentivisation.md | 4 ++-- FURPS/core/rln_smart_contract.md | 2 +- .../define_incentivisation_for_rlnaas.md | 4 ++-- .../deploy_rln_onchain_tree_on_l2_testnet.md | 19 +------------------ 4 files changed, 6 insertions(+), 23 deletions(-) diff --git a/FURPS/core/incentivisation.md b/FURPS/core/incentivisation.md index b0daf31..4bf76a3 100644 --- a/FURPS/core/incentivisation.md +++ b/FURPS/core/incentivisation.md @@ -3,13 +3,13 @@ ## Functionality 1. RLNaaS clients proceed to pay RLNaaS providers for attaching RLN proof to published messages. -2. RLNaaS clients can assess of the quality of a provisioned RLNaaS and use it to build local reputation. +2. RLNaaS clients can assess the quality of a provisioned RLNaaS and use it to build local reputation. 3. RLNaaS clients can use local reputation of RLNaaS providers to select what provider to use. ## Usability 1. A consumer node can pay a service node for RLNaaS. -2. A consumer node can select an RLNaaS provider based on their price and local reputation. +2. A consumer node can select an RLNaaS provider based on local reputation. ## Reliability diff --git a/FURPS/core/rln_smart_contract.md b/FURPS/core/rln_smart_contract.md index fa4ebf0..c0c6765 100644 --- a/FURPS/core/rln_smart_contract.md +++ b/FURPS/core/rln_smart_contract.md @@ -4,7 +4,7 @@ 1. RLN rate limit can be defined in terms of multiple messages per epoch. 2. RLN rate limit is set at membership insertion -3. RLN initialization only requires Web3 RPC `call`s, no blockchain events are needed. +3. RLN proof generation and validation only requires Web3 RPC `call`s, no blockchain events or initialisation are needed. 4. An ERC-20 token deposit is needed to insert a membership ## Usability diff --git a/draft-roadmap/define_incentivisation_for_rlnaas.md b/draft-roadmap/define_incentivisation_for_rlnaas.md index 39009ca..c51970d 100644 --- a/draft-roadmap/define_incentivisation_for_rlnaas.md +++ b/draft-roadmap/define_incentivisation_for_rlnaas.md @@ -29,10 +29,10 @@ This is the first step to providing a sustainable way to scale the Status applic **FURPS**: - F1. RLNaaS clients proceed to pay RLNaaS providers for attaching RLN proof to published messages. -- F2. RLNaaS clients can assess of the quality of a provisioned RLNaaS and use it to build local reputation. +- F2. RLNaaS clients can assess the quality of a provisioned RLNaaS and use it to build local reputation. - F3. RLNaaS clients can use local reputation of RLNaaS providers to select what provider to use. - U1. A consumer node can pay a service node for RLNaaS. -- U2. A consumer node can select an RLNaaS provider based on their price and local reputation. +- U2. A consumer node can select an RLNaaS provider based on local reputation. - R1. A consumer prefers new providers to known unreliable providers. - R2. In a stable network, a client can find, pay and send a message via a RLNaaS provider (**Vac-QA**) in 90% of cases **(Vac-DST)**. diff --git a/draft-roadmap/deploy_rln_onchain_tree_on_l2_testnet.md b/draft-roadmap/deploy_rln_onchain_tree_on_l2_testnet.md index 4546477..6fcb161 100644 --- a/draft-roadmap/deploy_rln_onchain_tree_on_l2_testnet.md +++ b/draft-roadmap/deploy_rln_onchain_tree_on_l2_testnet.md @@ -21,7 +21,7 @@ It will then be possible to design the usage of RLN in Chat SDK. - 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 initialization only requires Web3 RPC `call`s, no blockchain events are needed. +- 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. @@ -53,23 +53,6 @@ It will then be possible to design the usage of RLN in Chat SDK. - [ ] Dogfood: link to dogfooding session/artefact - [ ] Docs: links to README.md or docs.waku.org (TBD) -## [Fallback strategy for Web3 RPC endpoints are implemented in nwaku]() - -**Owner**: nwaku - -**Feature**: [nwaku](/FURPS/application/nwaku.md) - -**FURPS**: - -- R1. Relay node can fallback to alternative RPC endpoints - if the primary Web3 RPC provider becomes unavailable. - -**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