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

Add a way to process events from blocks in the past #76

Merged
merged 12 commits into from
Feb 18, 2025

Conversation

lmcorbalan
Copy link
Collaborator

@lmcorbalan lmcorbalan commented Jan 31, 2025

fixes #74

This PR enables the solver to resume indexing from a specified historical block rather than only from the latest block. With this update, if the solver stops indexing for any reason, it can restart and continue processing from the last successfully processed block, ensuring no data gaps and improving overall reliability.

Copy link

vercel bot commented Jan 31, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
intents-framework-ui ⬜️ Ignored (Inspect) Visit Preview Feb 18, 2025 6:50pm

@lmcorbalan lmcorbalan requested a review from fernandomg January 31, 2025 19:15
@lmcorbalan lmcorbalan marked this pull request as ready for review February 14, 2025 18:08
@lmcorbalan lmcorbalan changed the base branch from main to mainnet-demo February 18, 2025 08:21
@lmcorbalan lmcorbalan merged commit 95da9f9 into mainnet-demo Feb 18, 2025
2 checks passed
@lmcorbalan lmcorbalan deleted the last-block-processed branch February 18, 2025 18:59
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

Successfully merging this pull request may close these issues.

Solver to read from last processed block after restarting
1 participant