Skip to content

BackFill StateSyncTxs#352

Merged
lucca30 merged 17 commits intomasterfrom
lmartins/backfill-state-sync-txs
Aug 1, 2025
Merged

BackFill StateSyncTxs#352
lucca30 merged 17 commits intomasterfrom
lmartins/backfill-state-sync-txs

Conversation

@lucca30
Copy link
Copy Markdown
Contributor

@lucca30 lucca30 commented Aug 1, 2025

Description

Backfill state sync txs

Changes

  • Bugfix (non-breaking change that solves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (change that is not backwards-compatible and/or changes current functionality)
  • New test case for remote devnet

@lucca30 lucca30 requested review from a team and cffls August 1, 2025 20:33
Copy link
Copy Markdown
Member

@manav2401 manav2401 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth re-using the db instance after opening and eth client as well to avoid opening them for every read/write.

@lucca30 lucca30 merged commit f9b7bfb into master Aug 1, 2025
2 of 5 checks passed
@lucca30
Copy link
Copy Markdown
Contributor Author

lucca30 commented Aug 1, 2025

Yes, completely agreed. But our first use case would be a 624 entries which was done in less than 20seconds. But it's definitely an improvement for future use cases

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.

3 participants