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

Reliable Store Protocol: Enforcing view consistency across store nodes #561

Closed
staheri14 opened this issue May 20, 2021 · 5 comments
Closed

Comments

@staheri14
Copy link
Contributor

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.

@staheri14 staheri14 self-assigned this May 20, 2021
@staheri14
Copy link
Contributor Author

staheri14 commented May 27, 2021

See this GH discussion for some initial solution ideas.
vacp2p/rfc#384

@oskarth
Copy link
Contributor

oskarth commented Jul 14, 2021

@staheri14 Can we link this to spec/research issue? Moving to icebox for now

Also above issue is a loop :D

@staheri14
Copy link
Contributor Author

staheri14 commented Jul 16, 2021

@staheri14 Can we link this to spec/research issue? Moving to icebox for now

@oskarth

Indeed, that is a spec/research issue. Is there a way to link it to spec?

Also above issue is a loop :D

Oh, right! fixed it :p vacp2p/rfc#384

@oskarth
Copy link
Contributor

oskarth commented Jul 16, 2021

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

@staheri14
Copy link
Contributor Author

Created a new issue under research repo vacp2p/research#74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants