Multi-VM runtime: EVM, SVM and DAML on one ledger

The Tenzro ledger runs three execution environments on one state: the EVM, the SVM and DAML. Block-STM executes transactions in parallel, and TNZO is native in all three. One ledger, three programming surfaces.

Why three runtimes

Picking a single virtual machine leaves someone out. The EVM is where most smart-contract tooling and token standards live. The SVM brings Solana programs and their tooling. DAML is how many regulated organisations model multi-party workflows. All three are in active use, so the ledger runs all three.

Each transaction names its runtime, and the ledger dispatches it to the matching executor. All three read and write the same state and settle under the same consensus, Tenzro DAG Consensus (TDC), our post-quantum consensus protocol.

One balance, three views

The naive approach is to mint a wrapped asset in every runtime and bridge between them. The ledger does not do that.

TNZO has one native balance. The EVM sees it through a token contract that reads and writes the native balance directly. The SVM sees it through an SPL Token adapter that maps SPL instructions onto the same balance. DAML sees it through a holding template with the standard two-step transfer flow. Three surfaces, one balance: no bridge risk between runtimes and no fragmented liquidity.

EVM

The EVM supports the standard precompiles, plus Tenzro precompiles that expose network primitives to contracts, such as TEE attestation checks, STARK proof verification and VRF verification. Tenzro precompiles run inside ordinary EVM transactions, so a contract can call them in the same call as any other logic. Smart accounts follow ERC-4337, with ERC-7579 validator modules for session keys, spending limits and social recovery, and ERC-8004 registries for agent identity, reputation and validation. See EVM.

SVM

Solana programs run on Tenzro with their tooling intact. The SPL Token program is mapped through the adapter, and deployed programs run natively in the executor. See SVM.

DAML

The DAML runtime ingests DAML commands and emits Canton-shaped events, so organisations can model agreements between parties with the same account keys, the same TNZO and the same settlement fees as the rest of the ledger. See DAML and Canton.

Parallel execution

Sequential execution does not scale. Block-STM runs transactions optimistically with multi-version concurrency control, detects conflicts, and re-executes only the transactions that conflict. If a block is dominated by conflicts, it falls back to sequential execution. Block time is deterministic, so every validator reaches the same result from the same inputs.

Fees

Fees follow an EIP-1559-style base fee that adjusts to demand. Part of each fee is burned and part goes to the treasury. TNZO has a fixed supply of 1,000,000,000, and validator rewards come from a finite genesis pool rather than new issuance. See Token economics.