Struct ValidationContext 

pub struct ValidationContext {
    pub height: u32,
    pub timestamp: u64,
    pub constants: NetworkConstants,
    pub coin_records: HashMap<Bytes32, CoinRecord>,
    pub ephemeral_coins: HashSet<Bytes32>,
}

L2 chain state for validation.

coin_records should contain only the coins being spent in this bundle, not the full UTXO set. The caller loads these from their database and passes them in. dig-clvm never touches storage directly.

Fields

height: u32

Current L2 block height.

timestamp: u64

Current block timestamp (seconds since epoch).

constants: NetworkConstants

DIG network constants (from dig-constants crate).

coin_records: HashMap<Bytes32, CoinRecord>

Coins being spent in this bundle (coin_id -> CoinRecord). Only the coins relevant to this validation — NOT the full UTXO set.

ephemeral_coins: HashSet<Bytes32>

Coins created by earlier bundles in the same block (ephemeral).

Implementations

impl ValidationContext

pub fn spend_flags(&self, extra: u32) -> u32

Execution flags for running a spend bundle at this context’s height.

Combines the height-activated hard-fork flags, mempool-mode strictness, and the caller’s extra flags.

This derivation must be done by the caller: chia-consensus 0.26 took a height argument and computed get_flags_for_height_and_constants(height, constants) | flags | MEMPOOL_MODE internally, but 0.36 dropped both the argument and the derivation. Passing the caller’s flags alone would silently execute spends under pre-hard-fork rules and outside mempool mode — a consensus divergence that still compiles.