From f950937372cf15e78ab7ee2d86b341647bf91518 Mon Sep 17 00:00:00 2001 From: Pavel Date: Mon, 17 Feb 2025 22:19:02 +0300 Subject: [PATCH] capped-bandwidth.md --- docs/research/research-and-studies/capped-bandwidth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/research/research-and-studies/capped-bandwidth.md b/docs/research/research-and-studies/capped-bandwidth.md index 007099c..db72c90 100644 --- a/docs/research/research-and-studies/capped-bandwidth.md +++ b/docs/research/research-and-studies/capped-bandwidth.md @@ -24,7 +24,7 @@ Quick summary of the evolution to solve this problem: ## Current Solution (RLN v2) The current solution to this problem is the usage of RLN v2, which allows to rate-limit `x` messages every `y` seconds. On top of this, the introduction of [WAKU2-RLN-CONTRACT](https://github.com/waku-org/specs/blob/master/standards/core/rln-contract.md) enforces a maximum amount of messages that can be sent to the network per `epoch`. This is achieved by limiting the amount of memberships that can be registered. The current values are: -* `R_{max}`: 160000 mgs/epoch +* `R_{max}`: 160000 msgs/epoch * `r_{max}`: 600 msgs/epoch * `r_{min}`: 20 msgs/epoch