make reorg handling backward looking if it has caught up with the chain #143
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Improved reorg handler block range calculation to support both forward and backward scanning based on the current sync state.
What changed?
getReorgCheckRangefunction to dynamically determine the block range for reorg checksHow to test?
TestReorgHandlerRangeIsForwardLookingWhenItIsCatchingUpTestReorgHandlerRangeIsBackwardLookingWhenItIsCaughtUpTestReorgHandlerRangeStartIs0WhenRangeIsLargerThanProcessedBlocksWhy make this change?
The previous implementation always scanned forward, which could miss reorgs when the system was caught up with the chain head. This change ensures more thorough reorg detection by adapting the scan direction based on the current sync state, improving the reliability of reorg detection.