d760add9f5
* fix typo in github url * reorder pages * create milestone pages * add content to milestone pages * add content to 2024 milestones page
1.8 KiB
| title | tags | date | |
|---|---|---|---|
| Scale 1 to 1 chat messages PoC |
|
2024-09-07 |
Milestone Scale 1:1 chat messages PoC
Due Date: 2024-11-30
Improved flexibility of the rate limit (from 1 msg/epoch to N msg/epoch), providing better dimensioning for bandwidth capping.
Moving from RLNv1 to RLNv2 to allow better bandwidth dimensioning in the network. This will allow a message allocation per hour or day per registered publisher, providing better statistical guarantees for network bandwidth usage.
Deliverable: RLNv2 in nwaku
Improved flexibility of the rate limit (from 1 msg/epoch to N msg/epoch), providing better dimensioning for bandwidth capping. Moving from RLNv1 to RLNv2 to allow better bandwidth dimensioning in the network. This will allow a message allocation per hour or day per registered publisher, providing better statistical guarantees for network bandwidth usage. Note this only concerns native libraries using nwaku.
Deliverable: Maturing RLN variables/parameters revision (staking, contract/chain, token) - roadmap
A review of RLN security parameters and functionality in preparation for mainnet deployment. Analyse RLN deployment in the Waku proto-network and evaluate its DoS protection performance as well as review with the Status app team the potential cost mode of RLN:
- Should staking be introduced, especially to improve resilience against adversarial membership registrations?
- Should slashing be introduced or does the existing gossipsub scoring method provide enough protection?
- Which chain or L2 should we target for memberships?
- What token should be used?
- Do we need a combination of msg/sec and msg allocation/day rate limiting?