You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently eth_getLogs returns only 25 results, because we are not setting a limit and it defaults to 25
To fix this we should check if there's a next query in the mirror node response and do those queries until we get all the logs. To limit the number of request we can also set the limit to 100, which is the current max for the mirror-node.
One problem with this solution is that in combination with this Issue #675 and filtering by block range (fromBlock -> toBlock) this could make getLogs very inefficient and slow
Steps to reproduce
Execute an eth_getLogs request for a block range that contains more than 25 logs
Additional context
No response
Hedera network
mainnet, testnet, previewnet
Version
all
Operating system
No response
The text was updated successfully, but these errors were encountered:
Description
Currently
eth_getLogs
returns only 25 results, because we are not setting a limit and it defaults to 25To fix this we should check if there's a
next
query in the mirror node response and do those queries until we get all the logs. To limit the number of request we can also set the limit to 100, which is the current max for the mirror-node.One problem with this solution is that in combination with this Issue #675 and filtering by block range (fromBlock -> toBlock) this could make getLogs very inefficient and slow
Steps to reproduce
Execute an
eth_getLogs
request for a block range that contains more than 25 logsAdditional context
No response
Hedera network
mainnet, testnet, previewnet
Version
all
Operating system
No response
The text was updated successfully, but these errors were encountered: