Expand description
Tempo consensus owned by the canonical in-memory chain.
Mining checks consensus metadata before committing execution and signs the final header in the same storage write guard that publishes its block. Cache commits and state-root computation do not hold the storage lock, so readers can still access the published chain.
Imports that change canonical history start an unsigned signing segment. Database snapshots remain usable, but reverting across that import boundary starts a new segment at the restored height. Snapshots within the current segment restore consensus exactly.
All live consensus mutations, including rotation RPCs, must acquire the database write lock before the storage lock. Mining retains that database guard from preparation through publication, preventing snapshots, rewinds, resets, imports, or rotations from changing the prepared height or key schedule. Only initialization before the backend is shared and private staged copies are exempt; publishing a staged copy still requires the database write lock. Consensus readers acquire the database read lock before storage.
Historical queries can use the trusted fork provider at or below its pinned height. They snapshot the provider, root, and known canonical hash together with local history, then release all guards before network I/O. Upstream blocks must match that canonical hash when known. An overlapping reset can complete while the request returns the old snapshot; upstream responses are never cached into the replacement chain. Upstream committees remain independent of the local development identity. Height-bounded forwarding does not establish an authenticated committee or ancestry chain from upstream history to locally signed blocks.
Locally mined fork headers seal the same partial account and storage trie used by proofs. Its snapshots live in a separate bounded history cache, sharing the execution history’s cache settings but preserving local trie membership through disk round trips. Only a canonical local certificate can select a snapshot. Rewinds remove orphaned proof states. Resets clear proof history before a replacement signing history starts.
Re-exports§
use super::Backend;🔒use super::state::StateRootCache;🔒use super::storage::BlockchainStorage;🔒use super::storage::InMemoryBlockStates;🔒use crate::eth::backend::db::MaybeFullDatabase;🔒use crate::eth::backend::tempo_consensus::TempoConsensus;🔒use crate::eth::backend::tempo_consensus::TempoConsensusIdentity;🔒use crate::eth::backend::tempo_consensus::TempoFinalization;🔒use crate::eth::error::BlockchainError;🔒use crate::eth::tempo_consensus::TempoCertifiedBlock;🔒use alloy_consensus::BlockHeader;🔒use alloy_consensus::Sealable;🔒use alloy_consensus::proofs::calculate_transaction_root;🔒use alloy_network::Network;🔒use alloy_primitives::Address;🔒use alloy_primitives::B256;🔒use alloy_primitives::U256;🔒use alloy_primitives::map::AddressMap;🔒use alloy_primitives::map::HashMap;🔒use alloy_provider::Provider;🔒use alloy_rpc_types::EIP1186AccountProofResponse as AccountProof;🔒use anvil_core::eth::block::Block;🔒use anvil_core::eth::block::canonical_block;🔒use anvil_rpc::error::ErrorCode;🔒use anvil_rpc::error::RpcError;🔒use parking_lot::Mutex;🔒use parking_lot::RwLock;🔒use parking_lot::RwLockUpgradableReadGuard;🔒use revm::database::DbAccount;🔒use std::fmt;🔒use std::num::NonZeroU64;🔒use std::sync::Arc;🔒use tempo_hardfork::TempoHardfork;🔒use tempo_primitives::TempoHeader;🔒
Structs§
- Tempo
Chain 🔒 - Local certificates, key schedule, and consensus snapshots for the current signing history.
- Tempo
Snapshot 🔒 - Consensus and the sealed head trie retained by an explicit EVM snapshot.