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

Deterministic database syncing among the peers using single hash #2

Open
vasa-develop opened this issue Mar 30, 2020 · 2 comments
Open
Labels
open discussion this issue is open for suggestions

Comments

@vasa-develop
Copy link
Member

vasa-develop commented Mar 30, 2020

As discussed with @vaultec81, we have the following issue with OrbitDB, which leaves peers out of sync, even if they think they are in sync.

If a node that hasn't synced all the data or cannot connect to the network will view a different database state. If that same node is hooked into a blockchain where any Dapp operations require the data to be the same across all nodes.

Here is a related issue discussion, but not totally aligned with this issue.

We are expecting a PR related to this issue in the upcoming release of OrbitDB (possibly 0.24.1).

This is an on going discussion. Feedback is welcomed.

@vasa-develop
Copy link
Member Author

vasa-develop commented Mar 30, 2020

Anything you guys want to add here @vaultec81, @aphelionz?

@vasa-develop vasa-develop added the open discussion this issue is open for suggestions label Mar 30, 2020
@aphelionz
Copy link

Nothing to add, just looking forward to seeing the PR! Anything we can do to make strong eventual consistency even stronger is welcome.

Thanks for including me here.

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

No branches or pull requests

2 participants