synchronization problem
Opened this issue · 3 comments
when syncing from scratch with the 4.4.0.0 wallet, the sync always stalls at block 5000.
corresponding error messages in the log are:
2020-07-03 10:51:58 ERROR: CheckBlock() : stake under min. required confirmations
2020-07-03 10:51:58 ERROR: ProcessNewBlock : CheckBlock FAILED for block 34a92f347447c1431ba6fc29a5dc54c3eb48ea5d6a1f09aa429a453cd8114c79
however, the 34a92f347447c1431ba6fc29a5dc54c3eb48ea5d6a1f09aa429a453cd8114c79 hash corresponds to the valid
block 5001...!
i've tried to start with a fresh 'wallet.dat', instead of my working one, but the behaviour does not change.
re-indexing is unsuccessful, too.
also, when syncing with the 4.3.3.0 wallet until blocks of april/may 2020 and then switch to the 4.4.0.0 wallet
the same error messages as above (ERROR: CheckBlock() : stake under min. required confirmations, ERROR: ProcessNewBlock : CheckBlock FAILED for block ..) are returned and syncing stalls.
moreover, frequently 'misbehaving' error messages are seen for valid 4.4.0.0 nodes:
2020-07-03 10:51:54 Misbehaving: x.x.y.z (800 -> 900)
xbi v 4.4.0.0
on windows 7 64 bit
We are aware of the problem and are working on a solution.
The current workaround is to use the bootstrap, available from https://github.com/sub307/XBI-bootstrap/releases to bypass the issue.
#7 should solve the issue
ok, thx a lot, this works fine for now.
can you elaborate on the occurrence of these problems ?
are old version nodes 'spoiling' the sync process ?
We had issues with the chain forking, so we implemented some extra checks on the blocks. Unfortunatly some older blocks (with block 5001 being the first) don't get accepted with these checks in place. Older nodes get disconnected, so they shouldn't be able to have any impact.