Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle advanced reorgs #10

Open
joshstevens19 opened this issue Jun 25, 2024 · 0 comments
Open

Handle advanced reorgs #10

joshstevens19 opened this issue Jun 25, 2024 · 0 comments

Comments

@joshstevens19
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant