Open joshstevens19 opened 4 months ago
At the moment, rindexer does not check for reorgs; it has a flag in the yaml https://rindexer.xyz/docs/start-building/yaml-config/contracts#reorg_safe_distance to have a safe distance, but it should also have built-in advanced reorg flagging.
Often, if you are on top of your head live indexing, reorgs can happen after your node provider broadcasts the block within a split second. This can cause missing logs alongside general reorgs, which can happen in x-depth after processing.
At the moment, rindexer does not check for reorgs; it has a flag in the yaml https://rindexer.xyz/docs/start-building/yaml-config/contracts#reorg_safe_distance to have a safe distance, but it should also have built-in advanced reorg flagging.
Often, if you are on top of your head live indexing, reorgs can happen after your node provider broadcasts the block within a split second. This can cause missing logs alongside general reorgs, which can happen in x-depth after processing.