Current network and published architecture
Litecoin and EVM chains use different execution models. LitVM publishes an Arbitrum Orbit/Nitro architecture intended to provide an EVM-compatible environment alongside BitcoinOS bridging and a phased settlement roadmap. LiteForge is the current testnet (chain ID 4441). A testnet deployment is not proof that every roadmap component, bridge, sequencer, proof system, settlement path, or mainnet parameter is live or final. Verify the current phase in LitVM’s official documentation before relying on an architectural claim.
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.
Do not collapse the roadmap into a security guarantee
LitVM’s published architecture describes Arbitrum Nitro execution plus Succinct SP1 validity proofs and phased Litecoin anchoring. Those components have different trust, liveness, settlement, and finality properties. Do not assume a transaction is currently settled on Litecoin, that a bridge is available for a particular asset, or that a marketing description proves decentralization. For a material transaction, identify the exact chain, bridge contracts, current settlement layer, upgrade controls, sequencer status, and withdrawal conditions from official sources.
EVM compatibility has documented differences
LitVM supports Solidity contracts and common Ethereum tooling, but “EVM-compatible” does not mean every Ethereum assumption is identical. LitVM’s official documentation identifies differences in block numbers, timestamps, gas limits, randomness, and cross-chain address behaviour. Test contracts against chain ID 4441 and the exact current network. Never carry testnet addresses, approvals, gas assumptions, or bytecode claims into a future mainnet deployment without a separate review.
How a transaction flows on LitVM
User sends a transaction
A wallet should show chain ID 4441, the exact target, function, value, and decoded parameters before the user approves a testnet transaction.
The network orders and executes it
The LiteForge execution environment processes the transaction. The exact sequencer and proving status is an operational network fact; check current official status rather than inferring it from this website.
The wallet receives a transaction hash
Use the source-pinned LiteForge explorer or an independently selected RPC to verify the receipt, status, block, sender, recipient, value, and logs.
Apply the current settlement assumptions
Confirmation on LiteForge is not a generic promise of Litecoin finality. For bridge or real-value decisions, verify the currently deployed settlement phase and its withdrawal/finality rules.
This is a testnet. A transaction receipt proves execution on the connected chain; it does not by itself prove a roadmap component, bridge backing, mainnet availability, or a particular finality guarantee.
What you can build on LitVM — DeFi, tokens, and beyond
An EVM-compatible testnet can be used to test token, exchange, governance, game, identity, and other smart-contract designs. Each application still needs its own security review, and a test deployment does not establish production readiness. LiteForge uses zkLTC as its native gas token. Testnet zkLTC is for testing and has no represented monetary value on this site. Fees, capacity, bridge support, and mainnet behaviour must be checked independently.