[1.8.0] New user DAO sync required 4 restarts to complete #5882
Comments
|
I saw the same with an old user directory. I haven't tried it 4 times yet, but after the second restart it is still popping up for me as well. |
|
The address that was causing this warnings for me is |
|
With a fresh user directory the initial DAO sync works just fine, but when I look at the DAO monitor it is complaining. What looks suspicious to me is that for block 712099 the hash is generated by the node itself, but for the next block it is taken from a Peer, which is kind of odd. |
When syncing from genesis the number of blocks are limited so we get the `onParseBlockCompleteAfterBatchProcessing` called each time when the received blocks are processed, and as we are not at wallet height we repeat requesting blocks. But the new check for the BTC recipient triggers a resync from resource call. We add now a check that we do this check only once the wallet is synced and our block height from dao state matches wallet blockheight.
Could you reproduce that? |
When syncing from genesis the number of blocks are limited so we get the `onParseBlockCompleteAfterBatchProcessing` called each time when the received blocks are processed, and as we are not at wallet height we repeat requesting blocks. But the new check for the BTC recipient triggers a resync from resource call. We add now a check that we do this check only once the wallet is synced and our block height from dao state matches wallet blockheight.
Description
Starting Bisq v1.8.0 with a fresh data directory, the initial DAO sync threw up a reboot popup 4 times.
Logs attached.
Steps to reproduce
Run Bisq release/v1.8.0 with a fresh data directory, connect to local bitcoind.
Expected behaviour
DAO sync fast and painless.
Actual behaviour
It required restart of the app 4 times; each after the message in the log
The RECIPIENT_BTC_ADDRESS is not as expected. The DAO state is probably out of sync and a resync should fix that issueScreenshots
Additional info
Once the BTC chain sync completed, the DAO sync seemed to go smoothly, see log after 4th restart.
bisq.log
The text was updated successfully, but these errors were encountered: