-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Deliverable] Reliability Protocol for Resource-Restricted Clients #186
Comments
Updated end date to 13/09/2024 to wait for @danisharora099 from vacation. Following items are leftovers that are WIP now with ready PRs:
UPD: we still wait for UPD2: as per discussion with @danisharora099 descoping from this deliverable waku-org/js-waku#2074 |
From PoV of js-waku we can resolve this deliverable as per comment - waku-org/js-waku#2154 Only important thing would be to follow up after @Ivansete-status there are two items that are not resolved on |
morning @weboko et al - @NagyZoltanPeter is currently working on those enhancements |
Project board: https://github.com/orgs/waku-org/projects/31/views/1
Define and implement a protocol that improves reliability in web and mobile environments.
In this particular instance, js-waku will be the reference implementation of the designed protocol to enable focus of the js-waku team on resource-restricted environment and of the nwaku team on relay and service node matters/usage.
This deliverable includes the implementation of this protocol in go-waku (nwaku excluded). Work should be done in parallel and feed from each other.
The intent is to compose light push, filter and store v3-beta in combination.
Epics
The text was updated successfully, but these errors were encountered: