Use getLogs directly instead of creating a filter and querying it #312
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.
Looks like an unintended change introduced in the ether to viem port for legacy sdk,
Creating an event filter on the node, and then querying it as 2 steps is unnecessary and has perf issues (causing timeouts in alchemy)
Instead of
createEventFilter
andgetFilterLogs
,we can use
getLogs
and pass the event filters with the call, and get typesafe results