[bisq-network/bisq] Connect to another seed if current seed does not have recent BSQ blocks (#2927)

[Devin Bileck]

We have received several reports of clients stuck/failing to synchronize the DAO state. In most cases we suggest to restart the client to resolve the issue. This may potentially be caused by issues with some seeds not up to date with BSQ blocks, as we have encountered a few times now. As a result, we need to ensure the client is resilient enough to detect and handle issues with seed nodes.

Currently, clients will connect to another seed if one is offline. But does not handle the situation where a seed is online but does not have recent BSQ blocks.

Therefore if a client is not receiving recent BSQ blocks from the current seed node, it should disconnect from that seed node and choose another seed node. Perhaps the client can compare blockheight with the BTC nodes to determine if it is up to date.

This may also help to prevent issues with missed mailboxmessages as a seed node that does not have recent BSQ blocks is likely unstable and could prevent messages from being delivered which can lead to disputes and in the worst case to wrongly closed disputes if an important dispute msg is lost.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/2927
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190627/d538643e/attachment-0001.html>