#[repr(u32)]pub enum ErrorCode {
Show 22 variants
ValidationFailed = 1,
PaymasterValidationFailed = 2,
PrePaymasterPreparationFailed = 3,
PayForTxFailed = 4,
FailedToMarkFactoryDependencies = 5,
FailedToChargeFee = 6,
FromIsNotAnAccount = 7,
InnerTxError = 8,
Unknown = 9,
UnexpectedVMBehavior = 10,
BootloaderOutOfGas = 11,
ValidationOutOfGas = 12,
TooBigGasLimit = 13,
NotEnoughGasProvided = 14,
MissingInvocationLimitReached = 15,
FailedToSetL2Block = 16,
FailedToAppendTransactionToL2Block = 17,
VMPanic = 18,
TracerCustom = 19,
FailedToPublishCompressedBytecodes = 20,
FailedBlockTimestampAssertion = 21,
GenericError = 0,
}Expand description
Auto-generated discriminant enum variants
Variants§
ValidationFailed = 1
§Summary
Account validation failed during execution.
§Description
This error occurs when the account validation step fails during the verification and execution of a transaction.
PaymasterValidationFailed = 2
§Summary
Paymaster validation failed.
§Description
This error is emitted when the paymaster validation process fails during transaction execution.
PrePaymasterPreparationFailed = 3
§Summary
Pre-paymaster preparation step failed.
§Description
This error occurs during pre-transaction paymaster preparation if the paymaster input is too short (less than 4 bytes) or its selector is unsupported.
PayForTxFailed = 4
§Summary
Payment for the transaction failed.
§Description
This error is emitted when the system fails to deduct the required fees for executing the transaction.
FailedToMarkFactoryDependencies = 5
§Summary
Failed to register factory dependencies for L1 transactions.
§Description
This error occurs when the system is unable to mark the factory dependencies for an L1 transaction in the known code storage. For L1 transactions, factory dependencies must be recorded as known to ensure that all required code components are available. A failure here may indicate that the dependency data is missing or malformed.
FailedToChargeFee = 6
§Summary
Transaction fee deduction failed.
§Description
This error is raised when the funds transferred to the bootloader are insufficient compared to the required fee (calculated as gasLimit * gasPrice). This may occur when the payer (account or paymaster) does not send enough ETH or when fee parameters are misconfigured.
FromIsNotAnAccount = 7
§Summary
The sender address is not a valid account.
§Description
This error occurs when a transaction is attempted from an address that has not been deployed as an account, meaning the from address is just a contract.
InnerTxError = 8
§Summary
An inner transaction error occurred.
§Description
Transaction reverted due to a contract call that failed during execution.
Unknown = 9
§Summary
An unknown error occurred.
§Description
This error is emitted when the system encounters an unspecified reason for halting.
UnexpectedVMBehavior = 10
§Summary
The bootloader encountered an unexpected state.
§Description
This error can be triggered by various bootloader anomalies such as mismatched fee parameters (e.g., baseFee greater than maxFeePerGas), unaccepted pubdata price, failed system calls (like L1 messenger or System Context), or internal assertion failures.
BootloaderOutOfGas = 11
§Summary
The bootloader has run out of gas.
§Description
This error occurs when the bootloader does not have enough gas to continue executing the transaction.
ValidationOutOfGas = 12
§Summary
The validation step ran out of gas.
§Description
Validation step of transaction execution exceeds the allocated gas limit.
TooBigGasLimit = 13
§Summary
The transaction’s gas limit is excessively high.
§Description
This error occurs when the gas limit set for the transaction is too large for the server to handle.
NotEnoughGasProvided = 14
§Summary
Insufficient gas for the bootloader to continue the transaction.
§Description
The bootloader checks if it can supply the requested gas plus overhead. If the remaining gas is below this threshold, it reverts.
MissingInvocationLimitReached = 15
§Summary
The transaction exceeded the allowed number of storage invocations.
§Description
This error occurs when the transaction makes too many missing invocations to memory, surpassing the allowed limit.
FailedToSetL2Block = 16
§Summary
Unable to set L2 block information.
§Description
System failed to set the necessary information for the L2 block during execution.
FailedToAppendTransactionToL2Block = 17
§Summary
Unable to append the transaction hash to the ongoing L2 block.
§Description
The system context call to record this transaction in the current L2 block failed. Common causes include invalid or corrupted L2 block data, insufficient gas, or unforeseen internal errors in the system context.
VMPanic = 18
§Summary
The virtual machine encountered a panic.
§Description
VM experiences a critical failure and panic during transaction execution.
TracerCustom = 19
§Summary
Tracer aborted the transaction execution.
§Description
Custom tracer used during transaction execution decides to abort the process, typically due to specific conditions being met.
FailedToPublishCompressedBytecodes = 20
§Summary
Unable to publish compressed bytecodes.
§Description
Emitted when the system fails to publish the compressed bytecodes during execution.
FailedBlockTimestampAssertion = 21
§Summary
Block timestamp assertion failed during the transaction.
§Description
This error often occurs if the transaction’s timestamp is behind the last known block or conflicts with expected chronological order.