Error response format
Standard JSON-RPC errors
| Code | Name | Description |
|---|---|---|
-32700 | Parse error | Invalid JSON in request body |
-32600 | Invalid request | Missing required JSON-RPC fields |
-32601 | Method not found | Method does not exist or is unsupported |
-32602 | Invalid params | Wrong parameter types or count |
-32603 | Internal error | Server-side processing error |
EVM-specific errors
| Code | Name | Description |
|---|---|---|
-32000 | Call exception | Contract call failed (reverted, out of gas, etc.) |
-32003 | Transaction rejected | Transaction validation failed |
3 | Execution reverted | Contract execution reverted with reason |
Edge RPC normalized errors
Edge RPC normalizes errors from upstream providers to consistent codes:| Code | Name | Description |
|---|---|---|
-32005 | Rate limit exceeded | Too many requests |
-32012 | Range too large | Block range in eth_getLogs too large |
-32014 | Missing data | Block, transaction, or state not found |
-32015 | Node timeout | Upstream node timed out |
-32016 | Unauthorized | Invalid or missing authentication |