docs(messaging): delivery track milestones fixes#414
Conversation
c0bd56a to
92a7a69
Compare
Ivansete-status
left a comment
Ivansete-status
left a comment
There was a problem hiding this comment.
LGTM! Thanks for it! 🙌
I'm just adding some nitpicks that I hope you find useful but I'm fine with the current proposal, and maybe we can tackle these comments in the future.
Cheers
|
|
||
| Resolve the architectural gap where LightPush service nodes share a single RLN quota with relay traffic, making LightPush non-functional under high-volume relay conditions. | ||
|
|
||
| Once done, Logos Messaging fleets should be able to become fully RLN-protected; edge nodes are required to get an RLN membership and send lightpush requests with RLN-proof attached; RLNaaS is discontinued. |
There was a problem hiding this comment.
Also important to strengthen the membership management mechanism. Keep working on something like the following seems interesting: https://rln.waku.org/
Also needed a mechanism to manage membership from mobile.
There was a problem hiding this comment.
@Ivansete-status as discussed in the call, what you describe is already part of our roadmap: logos-messaging/pm#353
We definitely need to simplify the usage of RLN. Perhaps it will be some kind of RLN membership API. But this is out of scope of RLN for Lightpush milestone, it doesn't depend on it.
| 3. **Store API** — Status still relies on Store nodes for history retrieval, community descriptions, profiles, and SDS-hinted missed messages. Either introduce a new Store API alongside Messaging API, or allow using low-level API from the same `liblogosdelivery`. | ||
| 4. **Test suite** — Messaging API is QA-approved. Involvement of DST for reliability testing. | ||
| 5. **Documentation** — comprehensive developer documentation on the API. | ||
| 1. **Store API** — Status still relies on Store nodes for history retrieval, community descriptions, profiles, and SDS-hinted missed messages. Either introduce a new Store API alongside Messaging API, or allow using low-level API from the same `liblogosdelivery`. |
There was a problem hiding this comment.
IMO we should implement the current Status' store query management inside Messaging API and make Status to only use liblogosdelivery library.
There was a problem hiding this comment.
We'll discuss and choose the approach when starting to work on this 👌
| - U3. Application does not need to do a Web3 RPC call for every tree change to generate or validate messages. | ||
| - U4. Application can transfer tokens and register membership with a single transaction. |
There was a problem hiding this comment.
We will need Annon Coms help.
Also, we need to perform stress tests to know well which are the RLN limits, e.g., max number of members.
There was a problem hiding this comment.
AnonComms will help with this, but I'll keep Delivery Team as owner.
@Ivansete-status do we have max number of members defined somewhere in the smart contract?
|
|
||
| This must be done carefully. Node operators and users should be notified. No disturbance should occur for network users. | ||
|
|
||
| **Done when**: Fleet deployments (`logos.dev`, `logos.test`) are updated. No newline at end of file |
There was a problem hiding this comment.
Before considering it as done I think we need to:
- Measure which is the maximum allowed members
- Simplify the membership management UX
There was a problem hiding this comment.
I think it is okay to keep existing UX for the initial version. Yes, it is difficult to start using RLN, but at least the network will be honestly protected.
Currently membership management is scheduled for Testnet 0.3, but this will be one of the first things to do there. And if we have room earlier, we can consider doing it before.
Co-authored-by: kaiserd <1684595+kaiserd@users.noreply.github.com>
365f3e8 to
50acf36
Compare
3 participants
Description
RLN for LightpushSubscribe APItoMessaging API — Developer Preview. The implementation is finished.Implement RLN membership managementmilestone toReliable Channel API — GADeploy RLN Contracts to Status L2 testnettoStatus: integrate Logos Chatmilestone