Read the architecture in layers
Four jobs behind one interface
Execution, ordering, proving and settlement answer different questions.
LitVM’s architecture documentation describes Arbitrum Nitro for EVM-compatible execution, Succinct SP1 for validity proofs and Espresso for transaction ordering. It presents a hybrid rollup design, with bridging and settlement handled through additional components. These are project-described architectural choices; LTC Media has not audited their deployment or benchmarked the claimed performance.
The separation is useful even to a nondeveloper. Execution asks what a transaction does. Ordering decides which transaction comes first. Proving supplies evidence that a computation followed the rules. Settlement determines where the resulting state becomes authoritative. A strong implementation has to make the connections between those jobs reliable as well as make each job work. Our diagram therefore uses four labeled layers and explicit boundaries. It deliberately avoids a single arrow marked “secured by Litecoin,” because that phrase would hide the distinct assumptions readers need to assess.
- Architecture description ≠ deployment audit.
- Ask where the authoritative state lives in the current phase.