Skip to content
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: enhance reliability thanks to StoreV3 #2819

Closed
Tracked by #3082
Ivansete-status opened this issue Jun 18, 2024 · 0 comments · Fixed by #2977
Closed
Tracked by #3082

feat: enhance reliability thanks to StoreV3 #2819

Ivansete-status opened this issue Jun 18, 2024 · 0 comments · Fixed by #2977
Assignees
Labels
effort/weeks Estimated to be completed in a few weeks

Comments

@Ivansete-status
Copy link
Collaborator

Ivansete-status commented Jun 18, 2024

Problem

GossipSub doesn't natively define a mechanism for ensuring the correct message delivery. With that, we need to have an additional layer to increase the likelihood that any message has been sent to the desired destination.

Suggested solution

Have an interaction with a store node where we check whether a bunch of recently sent messages had reached at least, the offending store node.

As a reference, we have the following implementation and we need to do the same but in nwaku: status-im/status-go#5217 . With that, status-go should be able to use nwaku.

At first, we will work on having this feature working in relay but is likely that we will need to extend it to light push as well.

Additional context

The following can help to have a better context of what is needed from Status PoV: status-im/status-go#5234

Acceptance criteria

Have a reliability mechanism, in relay, that deals with StoreV3 and is analog to: status-im/status-go#5217

Epic

Reliability Protocol for Relay - #3082

@Ivansete-status Ivansete-status self-assigned this Jun 18, 2024
@Ivansete-status Ivansete-status moved this to In Progress in Waku Jun 18, 2024
@gabrielmer gabrielmer added the effort/weeks Estimated to be completed in a few weeks label Jul 24, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Waku Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/weeks Estimated to be completed in a few weeks
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants