Network

Solana Runtime v2

The next-generation execution environment under development by Solana Labs to replace the original runtime with a more modular, formally specified, and performant architecture that cleanly separates the Solana Virtual Machine (SVM) from the core validator client. Runtime v2 is designed to enable the SVM to be embedded in non-validator contexts (e.g., rollups, SVM-compatible chains), improve program execution performance, and provide cleaner abstractions for program loaders. It underpins the broader SVM ecosystem strategy and the Agave validator client.

IDsolana-runtime-v2

Plain meaning

Start with the shortest useful explanation before going deeper.

The next-generation execution environment under development by Solana Labs to replace the original runtime with a more modular, formally specified, and performant architecture that cleanly separates the Solana Virtual Machine (SVM) from the core validator client. Runtime v2 is designed to enable the SVM to be embedded in non-validator contexts (e.g., rollups, SVM-compatible chains), improve program execution performance, and provide cleaner abstractions for program loaders. It underpins the broader SVM ecosystem strategy and the Agave validator client.

Mental model

Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.

Think of it as a building block that connects one definition to the larger Solana system around it.

Technical context

Place the term inside its Solana layer so the definition is easier to reason about.

Clusters, nodes, MEV actors, routing, and operating environments.

Why builders care

Turn the term from vocabulary into something operational for product and engineering work.

This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.

AI handoff

AI handoff

Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.

Solana Runtime v2 (solana-runtime-v2)
Category: Network
Definition: The next-generation execution environment under development by Solana Labs to replace the original runtime with a more modular, formally specified, and performant architecture that cleanly separates the Solana Virtual Machine (SVM) from the core validator client. Runtime v2 is designed to enable the SVM to be embedded in non-validator contexts (e.g., rollups, SVM-compatible chains), improve program execution performance, and provide cleaner abstractions for program loaders. It underpins the broader SVM ecosystem strategy and the Agave validator client.
Related: Solana Virtual Machine (SVM), Runtime
Glossary Copilot

Ask grounded Solana questions without leaving the glossary.

Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.

Explain this code

Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.

Ask a glossary-grounded question

Ask a glossary-grounded question

The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.

Concept graph

See the term as part of a network, not a dead-end definition.

These branches show which concepts this term touches directly and what sits one layer beyond them.

Branch

Solana Virtual Machine (SVM)

The Solana Virtual Machine—the execution environment that runs on-chain programs. SVM loads SBF bytecode, provides syscalls for account access and cryptographic operations, enforces compute budgets, and manages memory. The SVM is being modularized (via the SVM API) to enable use in rollups and other environments outside the main Solana validator.

Branch

Runtime

The component of the SVM responsible for loading programs, enforcing account access rules (ownership, writability, signer checks), managing compute budgets, and executing transactions. The runtime ensures programs can only modify accounts they own, charges rent, and enforces the 10MB per-transaction account data limit.

Next concepts to explore

Keep the learning chain moving instead of stopping at one definition.

These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.

Core Protocol

Solana Virtual Machine (SVM)

The Solana Virtual Machine—the execution environment that runs on-chain programs. SVM loads SBF bytecode, provides syscalls for account access and cryptographic operations, enforces compute budgets, and manages memory. The SVM is being modularized (via the SVM API) to enable use in rollups and other environments outside the main Solana validator.

Core Protocol

Runtime

The component of the SVM responsible for loading programs, enforcing account access rules (ownership, writability, signer checks), managing compute budgets, and executing transactions. The runtime ensures programs can only modify accounts they own, charges rent, and enforces the 10MB per-transaction account data limit.

Network

Stake Activation

The process by which newly delegated stake becomes active and begins earning staking rewards. After a user delegates SOL to a validator, the stake enters a warmup phase and becomes fully active at the next epoch boundary (within one epoch, approximately 2-3 days). During activation, the stake does not contribute to the validator's voting weight or earn rewards. This delay prevents rapid stake shifts that could destabilize consensus.

Network

Slashing

The punitive reduction of a validator's stake as a penalty for provable misbehavior such as double-signing or equivocation — confirming two conflicting blocks at the same slot. As of 2025, Solana does not yet enforce automatic on-chain slashing (unlike Ethereum), though it is a planned addition to the protocol; the primary deterrents currently are social consensus, stake withdrawal by delegators, and future slashing implementation. The lack of slashing means Solana validators face lower direct financial risk from bugs but also reduced cryptographic accountability compared to slashing-enabled networks.

Related terms

Follow the concepts that give this term its actual context.

Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.

Core Protocolsvm

Solana Virtual Machine (SVM)

The Solana Virtual Machine—the execution environment that runs on-chain programs. SVM loads SBF bytecode, provides syscalls for account access and cryptographic operations, enforces compute budgets, and manages memory. The SVM is being modularized (via the SVM API) to enable use in rollups and other environments outside the main Solana validator.

Core Protocolruntime

Runtime

The component of the SVM responsible for loading programs, enforcing account access rules (ownership, writability, signer checks), managing compute budgets, and executing transactions. The runtime ensures programs can only modify accounts they own, charges rent, and enforces the 10MB per-transaction account data limit.

More in category

Stay in the same layer and keep building context.

These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.

Network

Mainnet Beta

Solana's primary production cluster where real SOL and real economic activity occur; the "beta" designation reflects the network's ongoing protocol development despite being fully live since March 2020. It uses the same architecture as other clusters but with real validator stakes, live staking rewards, and permanent on-chain state. All production dApps, tokens, and NFTs exist on Mainnet Beta.

Network

Devnet

A persistent public Solana cluster intended for application development and testing, running the same software version as Mainnet Beta but with no real economic value. Devnet SOL can be freely airdropped via the CLI or faucet APIs, and the ledger may be reset periodically by Solana Labs. Developers use Devnet to test programs and integrations before deploying to Mainnet Beta.

Network

Testnet

A public Solana cluster used primarily by the Solana core team and validators to test new software releases, performance benchmarks, and network upgrades under real network conditions before they reach Mainnet Beta. Testnet SOL has no monetary value, and the ledger is reset more frequently than Devnet; it is less suitable for application development and more suited for validator operators validating their infrastructure.

Network

TPS (Transactions Per Second)

The rate at which a Solana cluster processes and commits transactions; Solana's theoretical maximum exceeds 65,000 TPS due to its parallel execution model, though real-world sustained throughput on Mainnet Beta typically ranges from 2,000–5,000 non-vote TPS under normal load. Vote transactions (used for consensus) make up a significant portion of all on-chain activity and are counted separately. High TPS is enabled by Proof of History timestamps, Sealevel parallel execution, and Gulf Stream mempool-less forwarding.