EmulatorBase

Index of applied transactions by hash, for O(1) lookup. Platform-specific state.

Ordered log of transactions applied to this emulator, in submission order (oldest first).

Unlike appliedTxs (hashes only), each entry retains the full transaction together with the slot it was applied at and the inputs it consumed (resolved against the pre-application UTxO set). This lets callers reconstruct chain history — e.g. walk the continuing outputs of an asset — without keeping their own submitted-transaction bookkeeping.

Ordering reflects submission order; under concurrent submission it is best-effort — the underlying ledger state transition is serialized, but the log append that follows it is not.

Hashes of all applied transactions. Held as a materialized set (kept in sync with appliedTxIndex by the platform implementations) so access is a plain O(1) field read rather than a per-call key-set view.

Clear the applied-transaction bookkeeping (appliedTxLog and appliedTxIndex), leaving the ledger state (utxos, certState, datums) untouched.

Synchronously submit a transaction with debug scripts for diagnostic replay.

Returns CardanoInfo for this reader.

This is always available synchronously after the reader is constructed. For emulators, this returns the current context. For remote providers like BlockfrostProvider, the CardanoInfo is fetched during async construction.

Returns the current slot number.

Evaluator mode the emulator runs Plutus scripts in (e.g. Validate vs EvaluateAndComputeCost). Exposed so snapshots such as ImmutableEmulator.fromEmulator can preserve it rather than silently reverting to the Context default.

Emulator uses parasitic EC since all operations are synchronous.

Fetches the latest protocol parameters from the network.

Find UTxOs using a type-safe query.

Look up the full applied-tx record (transaction + slot + spent inputs) by hash.

Look up a datum by its hash. Returns None if unknown.

Look up a previously applied transaction by hash, or None if it was never applied.

Submits a transaction to the network.

Submit a transaction with debug scripts for diagnostic replay.

When a release script fails with empty logs, the evaluator replays it using the debug script to produce diagnostic output.

Check the status of a transaction on the blockchain.

Default implementation checks for UTxOs from the transaction. For emulators without a mempool concept, this returns either Confirmed or NotFound.

Find a single UTxO by its transaction input.

Find all UTxOs at the given address.

Find UTxOs by a set of transaction inputs (fails with NotFound if not all are found).

Map over the Future effect using this reader's captured ExecutionContext.

Poll for transaction confirmation.

Default implementation for emulators: a single check is sufficient since confirmation is instant.

Query UTxOs using a lambda DSL.

Translates the lambda to a UtxoQuery at compile time and returns a builder that can be further configured before execution. Effect-polymorphic — the resulting .execute() returns the reader's own F[Either[UtxoQueryError, Utxos]], so the same call shape works on Future-typed providers (Blockfrost, JS) and direct-style providers (ox Id).

Example:

// Simple query — execute immediately
reader.queryUtxos { u =>
 u.output.address == myAddress
}.execute()

// With pagination and minimum total
reader.queryUtxos { u =>
 u.output.address == myAddress && u.output.value.hasAsset(policyId, assetName)
}.minTotal(Coin.ada(100)).limit(10).execute()

Supported expressions:

• u.output.address == addr — query by address
• u.input.transactionId == txId — query by transaction
• u.output.value.hasAsset(policyId, assetName) — query/filter by asset
• u.output.value.coin >= amount — filter by minimum lovelace
• u.output.hasDatumHash(hash) — filter by datum hash
• && — AND combination
• || — OR combination

Submit a transaction and poll until confirmed.

Default implementation composes submit and pollForConfirmation.