LEVM, L1: Design EVM trait to standardize the vm's crate interface

[ilitteri]

Abstract

Define a trait EVM in crates/vm/vm.rs with methods execute_block, execute_tx, get_state_transitions

Motivation

Spec

Trait EVM

pub trait EVM {
    /// The error type for this trait's error. `EvmError` is the default, but it could be modified if needed.
    type Error = EvmError;

    /// Output for `execute_block`. The default is `(Vec<Receipt>, Vec<AccountUpdate>)`, but it could be modified if needed.
    type BlockExecutionOutput = (Vec<Receipt>, Vec<AccountUpdate>);

    /// Input for `execute_tx`. This must be defined by the implementor. It may vary depending on the backend EVM.
    type TransactionExecutionInput;

    /// Output for `execute_tx`. This must be defined by the implementor. It may vary depending on the backend EVM.
    type TransactionExecutionResult;

    /// Input for `get_state_transitions`. This must be defined by the implementor. It may vary depending on the backend EVM.
    type GetStateTransitionsInput;

    /// Executes every transaction of a block returning a list of their receipts executed and a list of accounts that were updated in the execution.
    fn execute_block(block: &Block, state: &mut EvmState) -> Result<Self::BlockExecutionOutput, Self::Error>;

    /// Executes a transaction returning its execution result. It may vary depending on the EVM used.
    fn execute_tx(input: Self::TransactionExecutionInput) -> Restult<Self::TransactionExecutionResult, Self::Error>;

    fn get_state_transitions(input: Self::GetStateTransitionsInput) -> Vec<AccountUpdate>;
}