The recent modification in INFURA API could produce the error like the following:
{"jsonrpc":"2.0","id":1,"error":{"code":-32005,"message":"query returned more than 1000 results"}}if eth_getLogs requests deal with a wide block frame. It could cause an issue when no events could be received if the number of block observed by a watcher was reset to a very old block (e.g. there are already more than 2000 Deposit events on the POA20 Bridge).
Similar issue appeared in the token bridge monitor recently: omni/bridge-monitor#24.
As possible solution it was suggested to use the binary search algorithm to narrow the block range for every request as so several requests will be performed.
The recent modification in INFURA API could produce the error like the following:
{"jsonrpc":"2.0","id":1,"error":{"code":-32005,"message":"query returned more than 1000 results"}}if
eth_getLogsrequests deal with a wide block frame. It could cause an issue when no events could be received if the number of block observed by a watcher was reset to a very old block (e.g. there are already more than 2000 Deposit events on the POA20 Bridge).Similar issue appeared in the token bridge monitor recently: omni/bridge-monitor#24.
As possible solution it was suggested to use the binary search algorithm to narrow the block range for every request as so several requests will be performed.