Expand description
Backing databases.
A backing database only serves reads that miss evm2βs accepted-state overlay. Fork lifecycle,
snapshots and cheatcode policy live in ForkRegistry and
ExecutionLifecycle, not here.
Re-exportsΒ§
use crate::fork::prefetch;πuse alloy_network::Network;πuse alloy_primitives::Address;πuse alloy_primitives::B256;πuse alloy_primitives::Bytes;πuse alloy_primitives::U256;πuse alloy_primitives::map::B256Map;πuse evm2::DatabaseError;πuse evm2::bytecode::Bytecode;πuse evm2::evm::AccountInfo;πuse evm2::evm::Cache;πuse evm2::evm::DbResult;πuse evm2::evm::DynDatabase;πuse evm2::evm::EmptyDB;πuse evm2::evm::InMemoryDB;πuse evm2::evm::NonStaticAny;πuse evm2::interpreter::Word;πuse foundry_fork_db::ForkBlockEnv;πuse parking_lot::RwLock;πuse std::any::TypeId;πuse std::sync::Arc;πuse std::sync::atomic::AtomicBool;πuse std::sync::atomic::Ordering;π
StructsΒ§
- Accepted
View π - A contextβs accepted state layered over its backing database, shared without copying.
- Fork
Code - Converts accounts of the fork cache, which holds raw code, into evm2 accounts.
- ForkDb
- A remote forkβs backing database: Foundryβs RPC-backed fork cache, read by evm2.
TraitsΒ§
- Backing
Db - A shareable backing database: every fork and every nested transaction reads through its own handle to the same source.
- Foundry
Database - Database view the factory needs at construction time.
FunctionsΒ§
- existing_
account - Returns
account, which a database reports as an existing empty account when it does not hold it, as an execution applying EIP-161 or not loads it. Under EIP-161 an empty account does not exist, so it is loaded as absent. - fatal π