[bisq-network/bisq] [1.7.0] DAO gets out of sync once or twice a day (#5595)

[Daniel Dawson]

It happened again. It won't tell me which node(s), or at least I don't know how to get that info. (Could it be because "Full-mode DAO state monitoring" is off?) It just says, "Your local data is not in consensus with at least one seed node. Please resync the DAO state."

It may be worth noting, however, under "Chain of DAO state hashes", even when it doesn't show a conflict with seed nodes, there are many blocks showing conflicts. At this point, the last 283 blocks (718061–718343) have anywhere from 2 to 13 conflicts. Hash creator is "self" for all of them, while for those without conflicts (except the last), it's "peer". It appears as though it's building up conflicts with peers, until eventually it conflicts with a seed.

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

Message ID: <bisq-network/bisq/issues/5595/1011391517 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220112/d1dd61c8/attachment.htm>