Call depth has exceeded the limit (if any)
Contract validation has failed (e.g. due to EVM 1.5 jump validity, Casper's purity checker or ewasm contract rules).
Generic execution failure.
EVM implementation generic internal error.
The designated INVALID instruction has been hit during execution.
The EIP-141 (https://github.com/ethereum/EIPs/blob/master/EIPS/eip-141.md) defines the instruction 0xfe as INVALID instruction to indicate execution abortion coming from high-level languages. This status code is reported in case this INVALID instruction has been encountered.
Tried to read outside memory bounds.
An example is RETURNDATACOPY reading past the available buffer.
The execution has run out of gas.
A call to a precompiled or system contract has ended with a failure.
An example: elliptic curve functions handed invalid EC points.
The execution of the given code and/or message has been rejected by the EVM implementation.
This error SHOULD be used to signal that the EVM is not able to or willing to execute the given code type or message. If an EVM returns the ::EVMC_REJECTED status code, the Client MAY try to execute it in other EVM implementation. For example, the Client tries running a code in the EVM 1.5. If the code is not supported there, the execution falls back to the EVM 1.0.
Execution terminated with REVERT opcode.
In this case the amount of gas left MAY be non-zero and additional output data MAY be provided in ::evmc_result.
The execution has attempted to put more items on the EVM stack than the specified limit.
Execution of an opcode has required more items on the EVM stack.
Tried to execute an operation which is restricted in static mode.
Execution finished with success.
An undefined instruction has been encountered.
Generated using TypeDoc
Execution has violated the jump destination restrictions.