You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This results in the next block being downloaded against the old branch, and issues like discussed here: #493 (comment)
Guess there should not be any expectation wrt the the announcements showing up in any particular order from the network. But wanted to understand what could be causing this.
So blocks are announced when the import notification is received. I was wondering if the recent changes to verify blocks in parallel could cause this kind of behavior, when reorg happens in rapid succession (like in this case)?
The text was updated successfully, but these errors were encountered:
This behavior is observed when peers are undergoing reorg quickly. The announcements appear reordered, or in random order.
Example:
This results in the next block being downloaded against the old branch, and issues like discussed here: #493 (comment)
Guess there should not be any expectation wrt the the announcements showing up in any particular order from the network. But wanted to understand what could be causing this.
So blocks are announced when the import notification is received. I was wondering if the recent changes to verify blocks in parallel could cause this kind of behavior, when reorg happens in rapid succession (like in this case)?
The text was updated successfully, but these errors were encountered: