[bisq-network/bisq] Unsynced DAO state forcing to restart Bisq in order to fix sync (Issue #6073)

[jmacxx]

> And it doesn't matter how often you restart the node to get everything in-sync?

In the tests I've done so far, it has not gone back into sync after restarting, only when the user explicitly rebuilds the DAO state.  I tried waiting 30 blocks in case the snapshot process somehow would fix it, but it did not.  The DAO state of the v1.8.2 loaded as in the example above is missing 4 param changes and 675 spent BSQ tx.

About 33% of all network nodes currently have their most recent DAO hashes not in consensus. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/6073#issuecomment-1067501919
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/issues/6073/1067501919 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220314/ba681a2e/attachment.htm>