The problem with bringing smart contracts to Litecoin
Bitcoin and Litecoin were designed as payment networks first. Adding programmability to BTC or LTC is hard because the base chains are UTXO-based, not account-based — and they prioritise security and simplicity over expressiveness. The naive solution is a sidechain. But most sidechains rely on federation multisigs or trusted validators, which introduces a single point of failure. If the validator set is compromised or dishonest, funds can be stolen. LitVM takes a different approach: validity proofs.
LitVM is currently on testnet. The addresses, contracts, and tokens described here are on the LitVM test network (chain ID 4441), not the Litecoin mainnet.
Validity proofs — trustless compression
A validity proof is a cryptographic certificate produced by a prover (the sequencer) that proves every state transition on LitVM was computed correctly. Unlike fraud proofs (Optimism/Avalanche), validity proofs make invalid states mathematically impossible — not just economically disincentivised. The proof is tiny: a few hundred bytes. Anyone can verify it against the Litecoin root, without re-executing all the transactions. This means: • Litecoin nodes don’t need to process every LitVM transaction • Security inherits directly from Litecoin — no separate validator set • Finality is as fast as the next Litecoin block
EVM compatibility
LitVM is EVM-equivalent — Solidity contracts, Hardhat, Foundry, and all standard Ethereum tooling work out of the box. This is a deliberate design choice: the hardest part of building a Layer 2 isn’t consensus, it’s getting developers to port their code. By speaking EVM natively, LitVM can absorb the existing Ethereum developer ecosystem without requiring any code changes. Your Hardhat config works. Your OpenZeppelin contracts work. Your existing Web3.js or viem frontends work.
How a transaction flows on LitVM
User sends a transaction
A user interacts with a dApp — say, swapping tokens on a LitVM DEX. Their transaction goes to a sequencer, which orders it and executes it against the current state.
The sequencer generates a proof
After batching a set of transactions, the sequencer runs the execution trace through a ZK prover (Groth16) to generate a validity proof. This proof certifies that all state transitions in the batch were computed correctly.
The proof is posted to Litecoin
The proof (a few hundred bytes) plus a minimal state diff are posted as a single Litecoin transaction. Litecoin validators or full nodes verify the proof without re-running the transactions.
State is finalized
Once the proof is accepted on Litecoin, the corresponding LitVM state is considered final. There is no challenge period, no fraud window — just cryptographic truth.
Because LitVM state is secured by cryptographic proofs rather than economic games, it’s safe to use with much shorter confirmation times than optimistic rollups. Always confirm against your own risk tolerance.
What you can build on LitVM
LitVM supports the full EVM instruction set, which means: • **DeFi protocols** — DEXs, lending markets, yield aggregators • **Token standards** — ERC-20, ERC-721 (NFTs), ERC-4626 (vaults) • **Cross-chain bridges** — trustless bridges using Litecoin as the settlement layer • **Gaming** — on-chain game state, asset ownership • **Identity** — ENS-style naming, credential systems The gas fees are paid in zkLTC, and because the proof compresses the data published to Litecoin, costs stay low even when the chain is busy.