-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: SDK: Reliable Message Subscription API for lightClient protocols #693
Comments
As per discussion here https://discord.com/channels/1110799176264056863/1111540684575477821/1145970002948792420 , some of the changes related to this would be part of app-sdk/chat-sdk team. |
Per discussion during message reliability call 2024-01-02, this is a generalized ticket and not directly pertinent to the Status x Waku integration. |
Closing this issue as it is already being addressed via new filterManager and storev3 based reliability for status. |
Summary
Refer to below issue from js-waku to get an idea.
waku-org/js-waku#1463
This requires further analysis as for go-waku we will have to include both cases of being used as light-client, service-node and also there should be a way to enable/disable these features for lightClients(because in some cases, a layer above go-waku must already be implementing some of these functionalities e.g: status-go).
Apart from the above, a way to enforce limits based on IP and message rate should also be implemented from a serviceNode point of view.
To be analyzed further to detail it down.
The text was updated successfully, but these errors were encountered: