Struct EvmSession 

pub struct EvmSession<'a> { /* private fields */ }

A session for executing multiple EVM operations without committing to the underlying DB.

Changes made within a session are tracked in the EVM’s journaled state. Call commit() to persist changes to the underlying database, or simply drop the session to discard all changes.

Note: For checkpoint/restore functionality across multiple transactions, use EvmCache::checkpoint() and EvmCache::restore() instead, as the EVM journal is cleared after each transaction.

Implementations

impl<'a> EvmSession<'a>

pub fn call_raw( &mut self, from: Address, to: Address, calldata: Bytes, commit: bool, ) -> Result<ExecutionResult>

Execute a call within the session.

If commit is true, changes are persisted to the session’s journaled state. If commit is false, the call is executed but its effects are immediately reverted.

Note: Changes are not persisted to the underlying CacheDB until commit() is called on the session itself.

pub fn commit(self)

Commit all session changes to the underlying database.

This persists all changes made during the session to the CacheDB.

pub fn evm( &mut self, ) -> &mut MainnetEvm<Context<BlockEnv, TxEnv, CfgEnv, &'a mut ForkCacheDB, Journal<&'a mut ForkCacheDB>, ()>>

Get access to the underlying EVM for advanced operations.

This exposes revm internals and bypasses the cache’s two-layer consistency model: state mutated directly through the journaled EVM lands in the session’s journal, not the BlockchainDb backend, and is only flushed to the CacheDB overlay on commit. Use with care.