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

[jmacxx]

### "`DAO state chain not connecting with the new data`" : 

Reproduced this one specific problem a few times - it is difficult to notice because it reports "`Your local node is in consensus with the network`" and everything looks good until ~10 minutes later when a new block arrives.  The chain of hashes remains stalled at last snapshot and everything else in the app looks ok: DAO synced, last verified block matches BitcoinJ block number.  

![image](https://user-images.githubusercontent.com/47253594/156828951-3bc6baa3-3fb1-4134-adf7-98525827801f.png)



- If the user leaves the issue / is unaware / **does not** rebuild DAO state from resources, then at next restart it catches up the blocks downloaded from seednode and complains that hash chains don't match.  Leaving the issue longer, it eventually reports that **everything is in sync** even though the hashchain is certainly not (as the hashchain comparison only looks a certain number of blocks back, 10 I think). 
- If you compare a known good hashchain against peers going back further you see a variable pattern of several hundred matching - not matching - matching hashes.  The not matching parts are always ones where the peer self-generated the hash, and the matching parts are ones where the hash was from seednode.   

Still investigating.


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

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