[bisq-network/bisq] Deactivate DAO state monitoring as it is too slow (Issue #5779)

[chimp1984]

I found a good compromise.
We can request the missing daoStateHashes from the seed node (we do that anyway for the past 10, I extend that to the missing number of hashes). We add those missing hashes to our list and mark them with a flag that we have not created them by ourslef (just informational). At every new block we create the hash ourself (the performance penalty of 200 ms is here not an issue). As the hash is created with the previous hash + the current dao state we would detect if our local dao state would be out of sync with the network, just as like we detect it if we would have created the missing hashes by ourself. We can do that also for the latest block, so we can be sure after sync that our local dao state is in sync.
This eliminates besically the problems with not having the DAO state monitored. We still leave the toggle in the preferences to enable/disable that kind of "full monitoring" mode. Seed nodes have that enabled by default and power users can/should od that as well. But for casual users there is basically no disadvantage to not have it enabled but removes the high performance degradation at syncing. 
   

-- 
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/5779#issuecomment-950899345
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211025/b04668b5/attachment-0001.htm>