Replies: 2 comments 3 replies
-
When you say it doesn’t not work, do you mean it gives an error or does it give empty array of events? Early times when blocks were less, you could do this, basically scan all the blocks from 0 to latest. But these days many chains produce lot of blocks, like every sec or even faster. So, it’s very resource consuming for a node to fulfil the queryFilter request (or eth_getLogs RPC which is internally made) that scans all the blocks and hence it has to give an error these days. Using a shorter block range like 10K or 1K should work. But if it gives an empty array, I think the contract address or network used is incorrect. |
Beta Was this translation helpful? Give feedback.
-
I have encountered a similar issue recently with
I remembered receiving Note: I did have to upgrade to ethers.js v5.7.2 to test the EtherscanProvider as the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
queryFilter doesn't work if i pass 0 to the fromblock. it works if i pass a correct fromblock. idk if its because of loading all the logs or what?
Beta Was this translation helpful? Give feedback.
All reactions