Definition: The Solana Virtual Machine (SVM) is the sandboxed execution environment in Solana’s runtime that runs on-chain programs compiled into Solana Bytecode Format (sBPF). It executes program instructions against the accounts supplied to a transaction and enforces runtime resource limits. The SVM is one part of Solana validator software; it is not a separate blockchain or an EVM-compatible environment by default.12
| Official documentation | Program Execution; Programs |
|---|---|
| Directories | Solana Directory |
In-Depth Explanation
From source code to an on-chain program
Developers generally write Solana programs in Rust and compile them with LLVM into an ELF file containing sBPF bytecode. The deployed program is stored in an executable account and invoked by instructions in transactions. A loader resolves and runs the program; the SVM provides the sandbox and runtime services needed for execution. sBPF is a Solana-specific variant of eBPF, not the standard eBPF format used by operating systems.12
Programs operate on accounts
A Solana program is stateless: its code is held in a program account, while mutable application state is kept in separate data accounts passed to instructions. Each instruction identifies a program, the accounts it may read or write, and instruction data. The runtime prepares that account context before calling the program. Account ownership rules limit which program can change account data or debit its lamports, so a program cannot freely rewrite another program’s state.23
Programs can invoke other programs through cross-program invocations (CPIs), allowing applications to compose token transfers, swaps, governance actions, and other operations. The runtime still checks account permissions and execution limits across those calls. The transaction either completes under its rules or fails; the SVM does not remove the need to validate program logic or account inputs.
Compute limits and execution
The runtime tracks work in compute units (CUs). A transaction receives a compute budget, and programs that exceed it fail rather than running without limit. Instruction data, account access, cryptographic operations, and CPIs all consume resources. The exact limits and feature set can change through protocol upgrades, so builders should consult the current documentation and test against the target cluster instead of treating one published number as permanent.1
How the SVM relates to Sealevel
Sealevel is Solana’s parallel runtime for on-chain programs. Solana transactions declare the accounts they read and write, which lets the validator identify transactions with compatible account access and execute those transactions concurrently. Transactions that need conflicting writes must be ordered appropriately. This scheduling model is a key part of Solana’s throughput design, but it does not mean every transaction or every instruction inside a transaction runs at the same time.45
“SVM” is now also used broadly for the program-execution environment or software used by Solana and by some independent networks. Reusing SVM software does not make another network part of Solana mainnet: it can have its own validator set, consensus, account state, upgrade process, and security assumptions. Check the particular network’s implementation before assuming programs or assets are portable.
SVM compared with the EVM
The SVM and the Ethereum Virtual Machine (EVM) execute different program formats and use different transaction and state models. A program written for one environment does not become compatible with the other simply because both are called virtual machines. Solana projects that offer EVM compatibility use a separate compatibility layer or implementation; that should be distinguished from Solana’s native SVM execution.
History
- September 8, 2019: Solana published its Sealevel explanation, describing a parallel runtime that uses each transaction’s declared account access to identify work that can run concurrently.5
- March 16, 2020: Solana Mainnet Beta launched. Solana’s May 2020 newsletter described that launch and the continuing work to enable smart contracts on the cluster.6
Page updated: November 12, 2026.
Related Terms
Related Articles
- Does Ethereum TPS Include Layer 2 Transactions?
- What Is MEV — And Why Every Ethereum Transaction Is a Game
- Are Layer 2 Networks Actually Decentralized?
- Why Smart Contract Audits Fail: What Post-Mortems Reveal About the Limits of Security Reviews
See Also
Sources
- Solana. “Program Execution.” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/core/programs/program-execution.
- Solana. “Programs.” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/core/programs.
- Solana. “Accounts.” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/core/accounts.
- Solana. “Terminology.” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/references/terminology.
- Solana Foundation. “Sealevel—Parallel Processing Thousands of Smart Contracts.” September 8, 2019. https://solana.com/news/sealevel—parallel-processing-thousands-of-smart-contracts.
- Solana Foundation. “May Newsletter.” June 24, 2020. Solana Media. https://solana.com/news/may-newsletter.