mirror of
https://github.com/logos-messaging/pm.git
synced 2026-01-07 16:43:06 +00:00
35 lines
791 B
Markdown
35 lines
791 B
Markdown
|
# RLN Smart Contract FURPS
|
||
|
|
|
||
|
|
## Functionality
|
||
|
|
|
||
|
|
1. RLN rate limit can be defined in terms of multiple messages per epoch.
|
||
|
|
2. RLN rate limit is set at membership insertion
|
||
|
|
3. RLN initialization only requires Web3 RPC `call`s, no blockchain events are needed.
|
||
|
|
4. An ERC-20 token deposit is needed to insert a membership
|
||
|
|
|
||
|
|
## Usability
|
||
|
|
|
||
|
|
1. Application developers can set RLN rate limit at insertion.
|
||
|
|
2. User do not need to wait for merkle tree synchronization and building to start relaying
|
||
|
|
or sending messages.
|
||
|
|
3.
|
||
|
|
|
||
|
|
## Reliability
|
||
|
|
|
||
|
|
1. ...
|
||
|
|
|
||
|
|
## Performance
|
||
|
|
|
||
|
|
1. ...
|
||
|
|
|
||
|
|
## Supportability
|
||
|
|
|
||
|
|
1. ...
|
||
|
|
|
||
|
|
## + (Privacy, Anonymity, Deployments)
|
||
|
|
|
||
|
|
1. Smart Contracts are deployed on Status Network Testnet.
|
||
|
|
2. TWN uses smart contracts deployed on Status Network Testnet.
|
||
|
|
3. Smart Contracts have been audited.
|
||
|
|
|