Add RLN integration in 2nd chat milestone

This commit is contained in:
fryorcraken 2025-06-11 11:45:30 +10:00
parent 8d033f56ee
commit c051dc973b
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
4 changed files with 23 additions and 1 deletions

View File

@ -23,6 +23,7 @@
1. Developers can create group conversations from Go Applications; available on pkg.go.dev.
2. Developers can create group conversations from Rust Applications; available on crates.io.
3. SDK can be instantiated with a RLN-enabled Waku node.
## + (Privacy, Anonymity, Deployments)

View File

@ -8,6 +8,7 @@
4. Messages can be flagged with three priorities level: critical, normal, optional.
5. When remaining message quota is low, critical messages are sent, normal messages are queued and optional messages are dropped.
6. When message quote is exhausted, critical messages are queued on top, normal messages are queued, optional messages are dropped.
7. Can consume RLN API to access rate limit and current quota.
## Usability

View File

@ -77,3 +77,23 @@ TODO: Clarify with Leonard
- [ ] Code: link to GitHub issues/PRs/Epic
- [ ] Dogfood: link to dogfooding session/artefact
- [ ] Docs: links to README.md or docs.waku.org (TBD)
### Enable usage with RLN SDK
**Owner**: App/Chat Dev
#### **Feature**: [Rate Limit Manager](/FURPS/application/rate_limit_manager.md)
**FURPS**:
- F7. Can consume RLN API to access rate limit and current quota.
#### **Feature**: [Group Chat](/FURPS/application/group_chat.md)
**FURPS**:
- S3. SDK can be instantiated with a RLN-enabled Waku node.
**Checklist**:
- [ ] Specs: link to specs and/or API definition
- [ ] Code: link to GitHub issues/PRs/Epic
- [ ] Dogfood: link to dogfooding session/artefact
- [ ] Docs: links to README.md or docs.waku.org (TBD)

View File

@ -4,7 +4,7 @@
- js-waku 31 Aug
**Resources Required for 2025H2**:
- 1 js-waku engineer, 31 Aug
- 2 js-waku engineer, 31 Aug
- 1.5 nwaku eng, 31 Aug (API)
- {external services consumed (Vac/IFT)}
- {infrastructure}