logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-02 14:13:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove old section

Browse Source
This commit is contained in:
fryorcraken.eth 2024-01-25 22:34:58 +11:00
parent 7ac5dcba1f
commit f2c90befc2
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
ROADMAP.md
View File

@ -65,7 +65,7 @@ Review the most important Waku RFCs:
- consider marking some specifications as "stagnant" indicating that they're not being focused on
- deprecate RFCs that are no longer relevant
### Store v3-beta - message hashes
### Store v3-beta - Message Hashes
- **Goal:** After this upgrade, the network will provide distributed and synchronised store services.
- **Research tracks:** Message Reliability
@ -199,13 +199,6 @@ a service node matching its desired set of content topics. Note that the cardina
(infinite) may be too high for integration into existing DHTs/shared discovery methods. Alternative approaches could
include advertising on a separate pubsub topic, advertisements published on the configured content topics, etc.
## Milestone: TWN - Rate-limiting Upgrade (RU)
**Goal:** After this upgrade, the network will show maturity in how it limits rate, with better dimensioning for
bandwidth capping, resource-restricted options and a clear evaluation of what is needed to improve DoS protection.
**[Research tracks:](https://www.notion.so/Waku-Research-ac7941c0ece84dc6b2948ec02b3cb695?pvs=21)** Secure Scaling, Restricted Run, Rate Limiting
**Estimated date of completion:** 30/09/2024
### RLN in resource-restricted clients
- **Goal:** Using RLN in resource-restricted provide fair user experience in terms of initial setup and performance.