Module Evm_node_lib_dev.Evm_state

Directory where the kernel logs are stored. The function execute below expect the directory to exist.

execute ?execution_timestamp ?simulation ~data_dir ?log_file ~wasm_entrypoint ~config evm_state messages executes the wasm_entrypoint function (default to kernel_run) with messages within the inbox of evm_state.

Kernel logs are stored under the kernel_logs_directory in log_file. simulation adds a prefix to the event to differenciate the logs.

When execution_timestamp is provided it's used as the l1 timestamp of in the Info_per_level message of the inbox, default value is `epoch`.

The execution is performed within a domain managed by pool.

init ~kernel initializes the local evm_state with kernel.

execute_and_inspect ~pool ~data_dir ?wasm_entrypoint ~config ~input evm_state executes the wasm_entrypoint function (default to kernel_run) with input within the inbox of evm_state, and returns input.insights_requests.

The execution is performed within a domain managed by pool.

current_block_height ~chain_family evm_state returns the height of the latest block produced by the kernel for chain_family.

Same as current_block_height for the block hash.

retrieve_block_at_root ~chain_family ~root evm_state reads the current block from durable storage at the given root path, decoding it using chain_family.

apply_unsigned_chunks ~data-dir ~config state chunks applies the blueprint chunks on top of evm_state. If the operation results in the production of a block, the new updated EVM state is returned along with the new block’s height. It is the responsibility of the caller to ensure the correctness of the chunks.

The data-dir is used to store the kernel logs in the kernel_logs_directory.

execute_single_transaction ~data_dir ~pool ~native_execution ~config evm_state block_in_progress hash txn calls the kernel entrypoint allowing to execute txn on top of evm_state, where txn is the block_in_progress.transactions_countth transaction of the next block.

execute_entrypoint ~data_dir ~pool ~native_execution ~config evm_state ~input_path ~input ~output_path ~entrypoint writes input to input_path in durable storage, calls the kernel entrypoint, and reads the result bytes from output_path.

assemble_block ~pool ~data_dir ~chain_family ~config ~timestamp ~number ~native_execution t builds an L2 block at height number and timestamp from the transactions previously accumulated in durable storage by the kernel instant-confirmation execution. No blueprint application is (re)performed; the function only assembles the block from already recorded effects and returns the result of this operation.

flag_local_exec evm_state adds a flag telling the kernel it is executed by an EVM node, not a rollup node.

clear_delayed_inbox evm_state removes the delayed inbox from the current EVM state.

irmin_store_path ~data_dir returns the path wherein the Irmin store is expected to be located, relatively to the data directory.

preload_kernel ~pool evm_state ensures the kernel of evm_state is added to the kernel cache of the execution runtime in use. This will speed-up the execution time for the first call of this kernel (typically in the context of a RPC call).

The execution of this command is performed within one of the domain managed by pool.

get_delayed_inbox_item state hash returns the delayed inbox content behind the hash hash. It fails if the hash does not exist or if the value cannot be decoded.

clear_block_storage chain_family block state removes the parent of block, and all durable storage information stored for block, if this function is called they need to be store elsewhere, mainly it consists in transactions.

clear_events state will remove events generated by the kernel from the durable storage of state.

delayed_inbox_hashes tree returns a list of hashes—each hash identifying an item of the delayed inbox.

This function will raise an exception if the delayed inbox is nowhere to be found.