AtHeartEngineer/rfc-index
1
0
Fork 0
mirror of https://github.com/vacp2p/rfc-index.git synced 2026-01-09 15:48:03 -05:00
Code Issues Packages Projects Releases Wiki Activity

sembr and enhance the motivation

Browse Source
This commit is contained in:
seugu
2026-01-02 16:20:31 +03:00
committed by GitHub
parent 9817f1936c
commit c14fe1c2eb
1 changed files with 22 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
vac/raw/multi-message_id-burn-rln.md
View File

@@ -10,23 +10,31 @@ contributors:
## Abstract ## Abstract
This document specifies multi-message_id burn RLN which the users This document specifies multi-message_id burn RLN which the users
can use their multiple message rights at once unlike previous versions of RLN. can use their multiple message rights at once unlike previous versions of RLN
that require a separate execution per `message_id`.
## Motivation ## Motivation
RLN is the decentralized rate limitting mechanism for anonymous networks. RLN is a decentralized rate-limiting mechanism designed for anonymous networks.
RLNv2, the latest version of RLN, the users can apply different rate limits In RLVv2, the latest version of the protocol, users can apply arbitrary rate limits
arbitrarily. This is possible with setting a rate limit over the `message_id`. by defining a specific limit over the `message_id`.
But this version lacks of usage of multiple message rights over this `message_id`. However, this version does not support the simultaneous exercise
Other saying, if the user wants to burn two different `message_id`, it need to compute of multiple messaging rights under a single `message_id`.
two separated proofs. This is not always fair since, if there are two big signal, In other words, if a user needs to consume multiple `message_id` units,
the users can send these two signal with burning only one `message_id`. they must compute separate proofs for each one.
The trivial solution would be the computing the multiple proof which cannot be the
efficient. This lack of flexibility creates an imbalance: users sending signals
This multiple burning feature may unlock the usage of RLN for big signals, of significantly different sizes still consume only one `message_id` per proof.
which can be a message or transaction in a single proof. While computing multiple proofs is a trivial workaround,
This document specifies the mechanism the users can burn multiple `message_id` for a it is neither computationally efficient nor manageable for high-throughput applications.
big signals at a single proof with changing existing RLNv2 circuit slightly.
Multiple burning refers to the mechanism where a fixed number of `message_id` units are processed
within the circuit to generate multiple corresponding nullifiers inside a single cryptographic proof.
This multiple burning feature may unlock the usage of RLN for big signals
such as large messages or complex transactions, by validating their resource consumption in a single proof.
This document specifies the mechanism that allows users to burn multiple `message_id` units
at once by slightly modifying the existing [RLNv2](./rln-v2.md) circuit.
## Format Specification ## Format Specification