AtHeartEngineer/rln-docs
1
0
Fork 0
mirror of https://github.com/Rate-Limiting-Nullifier/rln-docs.git synced 2026-01-08 23:08:09 -05:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 60f94e5e06

Browse Source
This commit is contained in:
curryrasul
2023-07-14 18:54:02 +00:00
parent c889728920
commit 0001bfd534
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
print.html
View File

@@ -256,7 +256,7 @@ We denote:
<p>It's sound, because if we use the same \(messageId\) twice - we'll share two different points from our first-degree polynomial, therefore it'll be possible to recover the secret key. And at the same time user also cannot input \(messageId\) value that's bigger than the \(messageLimit\), because of the range check.</p>
<h3 id="different-rate-limits-for-different-users"><a class="header" href="#different-rate-limits-for-different-users">Different rate-limits for different users</a></h3>
<p>It's also may be desired to have different rate-limits for different users, for example based on their stake amount. We can also achieve that by calculating \(userMessageLimit\) value and then deriving \(rateCommitment\):
\[rateCommitment = Poseidon(identityCommitment, rateCommitment)\]
\[rateCommitment = Poseidon(identityCommitment, userMessageLimit)\]
during the registration phase.</p>
<p>And it's the \(rateCommitment\) values that are stored in the membership Merkle tree.</p>
<p>Therefore, in the circuit users will have to prove that the:

2
rln_in_details.html
View File

@@ -202,7 +202,7 @@ We denote:
<p>It's sound, because if we use the same \(messageId\) twice - we'll share two different points from our first-degree polynomial, therefore it'll be possible to recover the secret key. And at the same time user also cannot input \(messageId\) value that's bigger than the \(messageLimit\), because of the range check.</p>
<h3 id="different-rate-limits-for-different-users"><a class="header" href="#different-rate-limits-for-different-users">Different rate-limits for different users</a></h3>
<p>It's also may be desired to have different rate-limits for different users, for example based on their stake amount. We can also achieve that by calculating \(userMessageLimit\) value and then deriving \(rateCommitment\):
\[rateCommitment = Poseidon(identityCommitment, rateCommitment)\]
\[rateCommitment = Poseidon(identityCommitment, userMessageLimit)\]
during the registration phase.</p>
<p>And it's the \(rateCommitment\) values that are stored in the membership Merkle tree.</p>
<p>Therefore, in the circuit users will have to prove that the:

2
searchindex.js
View File

File diff suppressed because one or more lines are too long

2
searchindex.json
View File

File diff suppressed because one or more lines are too long