Skip to content
LitVM AcademyStart
All modules
Blueprint badge, locked

Module 03 of 07

The LitVM Architecture

Arbitrum Nitro for execution, Succinct SP1 for proving, Espresso for sequencing, and a three phase path to Litecoin settlement.

13 min read, then 10 questions

LitVM is assembled from four independent pieces of infrastructure, each doing one job, plus a settlement plan that changes over time. This module names every component, explains why it is there, and walks the three phase migration that ends with Litecoin as the settlement layer.

The stack in one table

LayerTechnologyJob
ExecutionArbitrum NitroRun EVM smart contracts
ProvingSuccinct SP1 zkVMGenerate validity proofs of that execution
SequencingEspressoDecide transaction order, without a single operator
LTC bridgingBitcoinOS GrailMove LTC to and from the rollup trustlessly
EVM bridgingArbitrum BridgeMove ETH, stablecoins, and ERC-20s in
Gas tokenzkLTCPay for computation
Rollup operationsCalderaDeploy, host, and monitor the chain
SettlementEthereum, then LitecoinAnchor finality

Each row is a separate vendor with a separate failure mode. That is intentional: modular stacks let you replace one component without rewriting the others, which is exactly what the settlement migration requires.

Execution: Arbitrum Orbit and Nitro

LitVM is an Arbitrum Orbit chain. Orbit is the permissionless framework for launching chains that run the Nitro stack, the same software behind Arbitrum One.

What that buys:

  • EVM equivalence. Not "EVM compatible with caveats". Contracts compiled for Ethereum deploy unchanged, and Hardhat, Foundry, Remix, ethers.js, and viem all work as they do everywhere else.
  • Interactive fraud proofs. The dispute mechanism described in module two, already implemented and audited.
  • Calldata compression. Nitro compresses batches aggressively before posting, which is most of why fees stay low.
  • A custom gas token. Orbit chains can nominate their own native currency. LitVM nominates zkLTC instead of ETH, and that single configuration choice is what makes the Hard Money Web3 claim concrete rather than rhetorical.

Proving: Succinct SP1

SP1 is a general purpose zero knowledge virtual machine. It proves the execution of arbitrary Rust programs, which means it can prove the execution of the Nitro state transition function, because that function is written in Rust.

This is a meaningful shortcut. Traditional zkEVMs require rewriting the entire EVM as an arithmetic circuit, a multi-year effort that has to be repeated for every EVM upgrade. Proving an existing Rust implementation inside a general zkVM sidesteps that work entirely.

Consequences:

  • Finality in minutes. Once a proof verifies, the state is settled. No seven day window.
  • Proof cost of roughly $0.01 to $0.02 per transaction.
  • Recursive aggregation. Proofs of proofs let many batches collapse into a single verification, which is how the cost stays flat as volume grows.

Sequencing: Espresso

The sequencer decides what order transactions execute in. On most rollups it is a single server run by the team, which is the least decentralised part of the entire design. A centralised sequencer can censor transactions, reorder them for profit, and halt the chain by going offline.

Espresso replaces that with a shared sequencer: a permissionless network of nodes that reach consensus on ordering.

  • Censorship resistance. No single party decides what gets included.
  • Liveness. One node failing does not stop the chain.
  • Cross-chain composability. Chains sharing a sequencer can order operations atomically across both, which is the foundation for cross-rollup applications.

Operations: Caldera

Caldera is the rollup-as-a-service provider that deploys and runs the chain: RPC endpoints, the block explorer, the faucet, uptime monitoring. Every caldera.xyz URL in the network configuration comes from here.

This is infrastructure rather than protocol. It does not affect the trust model, but it is why the testnet has a working explorer and faucet from day one instead of six months in.

The two bridges

LitVM connects to two ecosystems, and the bridges are not equivalent.

BitcoinOS Grail, from Litecoin

  • Moves LTC in, mints zkLTC one to one
  • Trust model: ZK proofs, one honest verifier
  • Custodian: none
  • Purpose: onboard Litecoin holders

Arbitrum Bridge, from Ethereum

  • Moves ETH, USDC, USDT, and ERC-20s in
  • Trust model: optimistic plus ZK hybrid
  • Custodian: bridge contracts
  • Purpose: onboard EVM users and liquidity

The dual approach solves a real bootstrapping problem. Litecoin brings the monetary base and the community. Ethereum brings stablecoins, developers, and deep liquidity. A chain with only one of those does not get very far.

Module four covers the Grail bridge in full, because its security model is the most novel part of the whole system.

Three phases to Litecoin settlement

LitVM does not start as a Litecoin rollup. It becomes one. This is the part people most often get wrong.

  1. 01

    Phase 1: settlement on Ethereum

    A fully operational Orbit rollup posting state to Ethereum. Both bridges live, Espresso sequencing active, zkLTC as gas. Security comes from Ethereum plus SP1 validity proofs.

  2. 02

    Phase 2: proof anchoring to Litecoin

    Finalised batches are additionally anchored to Litecoin, with validity proofs inscribed using standard extended transactions. No Litecoin protocol change is required. This creates an audit trail that a Litecoin node can verify independently.

  3. 03

    Phase 3: native Litecoin settlement

    Settlement migrates off Ethereum. Litecoin becomes the canonical finality layer and LitVM becomes a fully native Litecoin rollup, secured by Scrypt proof of work.

Why not go straight to phase three? Because Ethereum already has mature rollup infrastructure, deep liquidity, and battle-tested bridge contracts. Starting there means the chain works on day one. The migration then happens under a running system rather than as a prerequisite for launching one.

Six layers of security

The litepaper enumerates them, and it is worth keeping the list straight because each one covers a different failure:

  1. Litecoin mainchain, fourteen years of proof of work above 2 PH/s.
  2. Ethereum settlement during phase one.
  3. ZK validity proofs from SP1, guaranteeing execution correctness.
  4. Espresso sequencing, preventing censorship and single-operator halts.
  5. BitcoinOS Grail, non-custodial bridging with a one-of-n honesty assumption.
  6. Arbitrum Bridge, established rollup bridge infrastructure.

Plus the operational layer: third party audits in progress, bug bounties, forced inclusion via the settlement layer, and emergency withdrawal paths.

Performance in context

MetricLitVMLitecoin L1Ethereum L1
ThroughputThousands of TPSAbout 56 TPSAbout 15 TPS
FeesSub-centSub-cent$1 to $100
FinalityMinutes, via ZK2.5 minutes12 or more minutes

Getting there relies on recursive zkSNARKs for proof aggregation, batching up to 10,000 transactions per rollup block, parallel proof generation, and calldata compression.

What to remember

  • 01LitVM is an Arbitrum Orbit chain running Nitro, with zkLTC nominated as the custom gas token instead of ETH.
  • 02Succinct SP1 proves the Nitro state transition function directly, avoiding a hand-built zkEVM circuit.
  • 03Espresso replaces the single-operator sequencer with a permissionless ordering network.
  • 04Caldera provides RPC, explorer, faucet, and monitoring, which is operations rather than trust.
  • 05Two bridges serve two ecosystems: Grail brings LTC trustlessly, the Arbitrum Bridge brings EVM assets and liquidity.
  • 06Settlement migrates in three phases: Ethereum first, then Litecoin proof anchoring, then native Litecoin settlement.
  • 07Six independent security layers cover six different failure modes, and fraud proofs remain as a fallback under the validity proofs.

Primary sources

Ready for the Blueprint?

Ten questions on this module. Answer 8 correctly and the badge unlocks. You can retake it as often as you like.

Take the quiz