Fix introduce retries if usdc tx fetching exceeds limits#275
Merged
Conversation
ii-cruz
force-pushed
the
iicruz/fix-usdc-max-tx-fetching
branch
from
July 16, 2025 16:26
4be36be to
b456665
Compare
ii-cruz
marked this pull request as ready for review
July 17, 2025 13:06
sisou
reviewed
Aug 5, 2025
Until the documented maximum no-log-limit range of 2000.
Recently, all queries with the old range started to fail and recommended this smaller range instead.
sisou
force-pushed
the
iicruz/fix-usdc-max-tx-fetching
branch
from
August 5, 2025 11:56
19293d6 to
32b21bc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces a mechanism to retry the request with a smaller block interval if there is an error.
This is an example of the error message we get where no more tx are fetched afterwards.
Query timeout exceeded. Consider reducing your block range. Based on your parameters and the response size limit, this block range should work: [0x42b950f, 0x435784f]Alchemy restricts log responses to 10k if the block range is >2000. So the safe query filter is tried with the provided block range, and if it fails, it attempts with a 2000 block range. If that still fails, it halves the range. https://www.alchemy.com/docs/deep-dive-into-eth_getlogs