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
{{ message }}
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
When EQS fetches contract events, it requests all events from block 0 to the latest block at once.
If the latest block number is very large or it has too many events, this request may be rejected by the node and the service will not start.
So it is recommended to start the query from the block which the contract deployed and limit the number of blocks per query.
The text was updated successfully, but these errors were encountered:
When EQS fetches contract events, it requests all events from block 0 to the latest block at once.
If the latest block number is very large or it has too many events, this request may be rejected by the node and the service will not start.
So it is recommended to start the query from the block which the contract deployed and limit the number of blocks per query.
The text was updated successfully, but these errors were encountered: