-
Notifications
You must be signed in to change notification settings - Fork 57
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
Reliable Store Protocol: Enforcing view consistency across store nodes #561
Comments
See this GH discussion for some initial solution ideas. |
@staheri14 Can we link this to spec/research issue? Moving to icebox for now Also above issue is a loop :D |
Indeed, that is a spec/research issue. Is there a way to link it to spec?
Oh, right! fixed it :p vacp2p/rfc#384 |
Usually just pasting the issue link will link it. In this case it is a discussion and for some reason it isn't linked automatically. It could be its own issue in research repo, but can't transfer issue since it is a separate org :p |
Created a new issue under research repo vacp2p/research#74 |
Currently, store nodes work independently without synchronizing the state of their persisted messages. As such, there might be situations that they may have different views of the historical messages. This view inconsistency also means that light nodes cannot rely on the completeness of the history provided by a single store node.
This issue is to provide a mechanism to synchronize the state of store nodes and enable them to exchange their views and converge to a consistent and complete state. This will add reliability to the overall store protocol service. Moreover, any single full store node becomes a reliable source of message history.
The text was updated successfully, but these errors were encountered: