Expand description
RPC Error codes and error objects
Constants§
- ACCOUNT_
ERROR - CALL_
EXECUTION_ ERROR - Call() execution error. This is clearly an application level error code, but we keep the error code to be ethereum rpc client compatible.
- CONFLUX_
PIVOT_ CHAIN_ UNSTABLE - DEPRECATED
- The requested feature is deprecated.
- ENCODING_
ERROR - Encoding error happened in signing structured data. Related to EIP712.
- EXCEPTION_
ERROR - Any exception happened while processing the transaction. Mostly likely there is an internal error within the server state.
- EXPERIMENTAL
- The requested feature is experimental.
- INCAPABLE
- The node is not able to serve the request due to configuration. e.g. Not mining, light node, not archive node.
- NO_
PEERS - No peers are currently connected or there is insufficient amount of peers connected.
- NO_
TRUSTED_ PEERS - No connection to trusted peers.
- POS_
NOT_ ENABLED - PREVIOUS_
REQUEST_ NOT_ FOUND - The error can be given to a request about a previous related request which we can not associate with.
- REQUEST_
REJECTED_ IN_ CATCH_ UP - When the node is still in catch up mode, it is not capable to handle certain requests. We will return this code in this situation.
- REQUEST_
REJECTED_ LIMIT_ DATA - When the request is considered too much for the rpc function. The consideration is set individually per rpc. It can be data too large, or it can be that some performance/security related parameter is outside the accepted range.
- REQUEST_
REJECTED_ TOO_ MANY_ REQUESTS - When there are too many rpc requests. We limit the number of allowed rpc requests for attack prevention.
- SUSPICIOUS_
MINING_ RATE - The node see a suspicious total mining power or block rate. It’s likely that the node is under attack or the whole Conflux network enters an abnormal state.
- UNSUPPORTED
- The request is not supported (yet) at this version.