You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: