acid-info
/
vac.dev
mirror of https://github.com/acid-info/vac.dev.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix typo

This commit is contained in:
Oskar Thoren 2019-11-12 11:05:53 +08:00
parent c4ac91def0
commit 7060b4578d
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_posts/2019-11-08-feasibility-semaphore-rate-limiting-zksnarks.md
View File

@ -66,7 +66,7 @@ In the case of rate limiting, we do want nodes to send multiple messages. This c
3. This means any untrusted user who detects a spamming user, can use it to access their private key corresponding to funds in the contract, and thus slash them. 3. This means any untrusted user who detects a spamming user, can use it to access their private key corresponding to funds in the contract, and thus slash them.
4. As a consequence of above, we have a system where registered users can only messages X times per epoch, and no one can see who is sending what messages. Additionally, if a user is violation the above rate limit, they can be punished and any user can profit from it. 4. As a consequence of above, we have a system where registered users can only messages X times per epoch, and no one can see who is sending what messages. Additionally, if a user is violating the above rate limit, they can be punished and any user can profit from it.
### Briefly on scope of 'approved users' ### Briefly on scope of 'approved users'