mirror of
https://github.com/Rate-Limiting-Nullifier/rln-docs.git
synced 2026-01-08 23:08:09 -05:00
deploy: 3b84d0a94c
This commit is contained in:
@@ -198,7 +198,7 @@
|
||||
<p><strong>RLN</strong> helps us identify and "kick" the spammer.</p>
|
||||
<p>Moreover, <strong>RLN</strong> can be useful not only to prevent spam attacks but, in general, to limit users (in anonymous environments) in the number of actions (f.e. to vote or to make a bid).</p>
|
||||
<h2 id="how-it-works"><a class="header" href="#how-it-works">How it works</a></h2>
|
||||
<p>The <strong>RLN</strong> construct's functionality consists of three parts These parts should be integrated by the upstream applications, that require anonymity and spam protection. The applications can be centralized or decentralized. For decentralized applications, each user maintains separate storage and compute resources for the application. </p>
|
||||
<p>The <strong>RLN</strong> construct functionality consists of three parts. These parts should be integrated by the upstream applications, that require anonymity and spam protection. The applications can be centralized or decentralized. For decentralized applications, each user maintains separate storage and compute resources for the application. </p>
|
||||
<p>The three parts are:</p>
|
||||
<ul>
|
||||
<li>registration;</li>
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -174,7 +174,7 @@
|
||||
<p><strong>RLN</strong> helps us identify and "kick" the spammer.</p>
|
||||
<p>Moreover, <strong>RLN</strong> can be useful not only to prevent spam attacks but, in general, to limit users (in anonymous environments) in the number of actions (f.e. to vote or to make a bid).</p>
|
||||
<h2 id="how-it-works"><a class="header" href="#how-it-works">How it works</a></h2>
|
||||
<p>The <strong>RLN</strong> construct's functionality consists of three parts These parts should be integrated by the upstream applications, that require anonymity and spam protection. The applications can be centralized or decentralized. For decentralized applications, each user maintains separate storage and compute resources for the application. </p>
|
||||
<p>The <strong>RLN</strong> construct functionality consists of three parts. These parts should be integrated by the upstream applications, that require anonymity and spam protection. The applications can be centralized or decentralized. For decentralized applications, each user maintains separate storage and compute resources for the application. </p>
|
||||
<p>The three parts are:</p>
|
||||
<ul>
|
||||
<li>registration;</li>
|
||||
|
||||
Reference in New Issue
Block a user