Developing decentralized applications (dApps) on EVM chains such as Ethereum, Binance Smart Chain (BSC), Polygon, and other compatible networks can be an exciting and rewarding experience. However, like any software development endeavor, you may encounter various errors and exceptions along the way. Let us look at the common errors you can encounter, what they mean and what you can do to prevent it.
Code | Message |
Explanation |
-32000 |
header not found could not find block xxx |
The requested block doesn't exist on the node. Invalid block number or the node you're hitting is not in sync yet. Use a retry mechanism with an incremental timeout |
-32000 |
stack limit reached 1024 (1023) |
Usually a smart contract error/bug |
-32000 |
method handler crashed |
Internal error from the blockchain client, can be a client bug. Write us a ticket so we can double check the nodes |
-32000 |
execution timeout |
Add the timeout param in your request to override the default client timeout. Read more about this here |
-32000 |
nonce too low |
The nonce value specified in your transaction is lower than the next valid nonce for the sender account. |
-32000 |
filter not found |
Filter exceeded timeout, you'll have to recreate the filter once more. Read about it here |
-32009 |
trace requests limited to x/sec |
We have limited the debug and trace method to a specific RPS to prevent the nodes from overloading |
-32010 |
Transaction cost exceeds current gas limit |
Gas limit is set too low |
-32011 |
network error |
This error occurs when there is a problem with the connection between the client and server, such as a timeout or a dropped connection |
-32015 |
VM execution error |
Smart contract execution error |
-32601 |
method not found |
Typically a typo in the method name, check for spelling errors |
-32601 |
failed to parse request |
Incorrect request body, please double check the method, params |
-32602 |
invalid argument 0: json: cannot unmarshal hex string without 0x prefix into Go struct field CallArgs.to of type common.Address |
Request not correct, 0x not added to the address. Add 0x before the hex |
-32602 |
eth_getLogs and eth_newFilter are limited to a 10,000 blocks range |
Read a in-depth explanation here |
-32603 |
Internal JSON-RPC error |
This error is typically due to a bad or invalid payload |
-32612 |
custom traces are blocked |
Submit a request here |
-32613 |
custom trace not found in allowed custom traces |
Submit a request here |
The RPC errors defined above are a collection of common errors you can encounter while developing on chains like ETH, BSC, Polygon, etc. These chains run on multiple clients with their own error definitions. You can view those errors in the source code as well
If you come across an unknown EVM error, feel free to reach out to the Support team.
Comments
0 comments
Article is closed for comments.