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

[jmacxx]

The significant data increase of account age witness records was a bug, fixed by https://github.com/bisq-network/bisq/pull/5974.  So that may have settled down by now, and it could be that we're back to the previous "normal" rate of consensus errors.  

The reminder popup was coded to show a maximum of once per bisq session; if we put a "do not show again" option, it would defeat the purpose which is to get all nodes in consensus.  I agree though, wording could be made nicer to explain cause and effect as was done in a related way here: https://github.com/bisq-network/bisq/pull/6063

The other questions @chimp1984 is best suited to answer.

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

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