Add blocksBatchSize param to useScaffoldEventHistory
#1118
Merged
Conversation
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
damianmarti
approved these changes
Jun 26, 2025
technophile-04
approved these changes
Jul 2, 2025
Collaborator
technophile-04
left a comment
technophile-04
left a comment
There was a problem hiding this comment.
Tested and workd nicely!! Thanks Rinat!
This was referenced Jul 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Default value is 500 since we're working mostly with alchemy. If users want to work with quicknode or other providers they can specify
blocksBatchSizefor their caseTo test do the same as in #1117 but also experiment with parameter
blocksBatchSizeto the useScaffoldEventHistory onapp/page.tsx.PR is to #1117 branch (I branched from it), so
toBlockalso works in this PRSecond part of #1110