Chain Reorg Detection and Handling

[LeoPatOZ]

Description:

Implement blockchain reorg detection to ensure event ordering consistency and data integrity during chain reorgs.

Implementation:

• Detect when a reorg occurs (block hash changes)
• Maintain recent block history (configurable depth, e.g., 12 blocks) We should actually do:
  • Reorg to depth specified in config
  • Do 1 check of parent hash, if it matches return depth --> start streaming from there
  • If not, recursively find parent hash match
  • Return match --> stream from there
• Re-process events from reorg point
• Ensure event ordering is maintained during reorg recovery
• Ensure reorg logic exists for both historical and live modes.

[0xNeshi]

Investigate how to optimize block range channeling on reorg detection, e.g. would it be possible to remove all of the pending block ranges that no longer exist post-reorg.

[0xNeshi]

Related #109