Replies: 1 comment
-
|
Hey @yoyoj1023! Thanks for a good question! As I remember, there were no limits previously, hooks just worked from any Created an issue #1110 so we can discuss details and start working on it Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I hope the parameter object of
useScaffoldEventHistory()can include a new variable called toBlock(or limitBlock), which is used to limit the number of logs fetched per request toeth_getLogs.For example, on the Alchemy dashboard, the
eth_getLogsmethod used to read blockchain events is often limited to a maximum of 500 blocks per request. If the request exceeds 500 blocks, an error will be returned:{ "jsonrpc": "2.0", "id": 48, "error": { "code": -32600, "message": "You can make eth_getLogs requests with up to a 500 block range. Based on your parameters, this block range should work: [0x0, 0x1f3]" } }Would it be a good idea to add a block range limitation (e.g., 500 blocks max) within the
useScaffoldEventHistory()hook to avoid such errors when querying logs?Beta Was this translation helpful? Give feedback.
All reactions