OGGlossary OSSolana vocabulary rebuilt for builders.
ENPT-BRES
Network

Bundle Simulation

The process of executing a Jito bundle against the current chain state in a sandboxed environment to verify that all transactions in the bundle succeed and produce the expected outcome before committing real tips and submitting to the Block Engine. Simulation catches issues like stale state, insufficient balances, or failed arbitrage conditions, preventing searchers from paying tips for bundles that would fail on-chain. Jito provides simulateBundle API endpoints for this purpose.

IDbundle-simulation
Plain meaning

Plain meaning

Start with the shortest useful explanation before going deeper.

The process of executing a Jito bundle against the current chain state in a sandboxed environment to verify that all transactions in the bundle succeed and produce the expected outcome before committing real tips and submitting to the Block Engine. Simulation catches issues like stale state, insufficient balances, or failed arbitrage conditions, preventing searchers from paying tips for bundles that would fail on-chain. Jito provides simulateBundle API endpoints for this purpose.

Mental model

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

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

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.

Bundle Simulation (bundle-simulation)
Category: Network
Definition: The process of executing a Jito bundle against the current chain state in a sandboxed environment to verify that all transactions in the bundle succeed and produce the expected outcome before committing real tips and submitting to the Block Engine. Simulation catches issues like stale state, insufficient balances, or failed arbitrage conditions, preventing searchers from paying tips for bundles that would fail on-chain. Jito provides simulateBundle API endpoints for this purpose.
Related: Bundle (Jito), Block Engine (Jito), Jito (MEV Infrastructure)
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.

Open full Copilot workspace
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

Bundle (Jito)

An atomic group of up to five transactions submitted together through Jito's Block Engine, where either all transactions land in sequence or none do, enabling MEV strategies that depend on guaranteed transaction ordering without risk of partial execution. Bundles are submitted with a tip to incentivize the leader to include them; the Block Engine simulates bundles, selects the most profitable ones, and forwards them to the Jito-enabled leader. Bundles land at the top of a block before standard transactions, giving searchers execution priority.

MEV (Maximal Extractable Value)Tip (Jito)
Open term
Branch

Block Engine (Jito)

Jito's off-chain infrastructure component that receives bundles from MEV searchers, simulates them against the current chain state to verify profitability and validity, and forwards the highest-value bundles to the current Jito-enabled leader just before block production. The Block Engine operates as a low-latency relay that continuously tracks the leader schedule and streams winning bundles in real time, acting as a private transaction ordering marketplace sitting between searchers and validators.

Open term
Branch

Jito (MEV Infrastructure)

A Solana MEV infrastructure project by Jito Labs that operates a modified validator client (jito-solana), a Block Engine for bundle simulation and routing, and a tip distribution program that collects and distributes MEV tips to staked validators. Jito's client is run by a supermajority of Solana's stake-weighted validators, making its bundle and tip market the de-facto MEV layer for the network. Jito also operates a restaking and liquid staking protocol (JitoSOL) using proceeds from MEV tip redistribution.

Open term
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.

Network

Bundle (Jito)

An atomic group of up to five transactions submitted together through Jito's Block Engine, where either all transactions land in sequence or none do, enabling MEV strategies that depend on guaranteed transaction ordering without risk of partial execution. Bundles are submitted with a tip to incentivize the leader to include them; the Block Engine simulates bundles, selects the most profitable ones, and forwards them to the Jito-enabled leader. Bundles land at the top of a block before standard transactions, giving searchers execution priority.

Open term
Network

Block Engine (Jito)

Jito's off-chain infrastructure component that receives bundles from MEV searchers, simulates them against the current chain state to verify profitability and validity, and forwards the highest-value bundles to the current Jito-enabled leader just before block production. The Block Engine operates as a low-latency relay that continuously tracks the leader schedule and streams winning bundles in real time, acting as a private transaction ordering marketplace sitting between searchers and validators.

Open term
Network

Jito (MEV Infrastructure)

A Solana MEV infrastructure project by Jito Labs that operates a modified validator client (jito-solana), a Block Engine for bundle simulation and routing, and a tip distribution program that collects and distributes MEV tips to staked validators. Jito's client is run by a supermajority of Solana's stake-weighted validators, making its bundle and tip market the de-facto MEV layer for the network. Jito also operates a restaking and liquid staking protocol (JitoSOL) using proceeds from MEV tip redistribution.

Open term
Network

Confirmation Time

The wallclock duration between a transaction being submitted and achieving a desired commitment level. On Solana, processed confirmation takes ~400ms (leader executes), confirmed (optimistic) takes ~400ms-1s (supermajority votes), and finalized (rooted) typically takes 26-32 slots (~10-13 seconds). Actual confirmation time varies with network congestion, leader distance, and transaction priority fee.

Open term
Commonly confused with

Terms nearby in vocabulary, acronym, or conceptual neighborhood.

These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.

Networkbundle

Bundle (Jito)

An atomic group of up to five transactions submitted together through Jito's Block Engine, where either all transactions land in sequence or none do, enabling MEV strategies that depend on guaranteed transaction ordering without risk of partial execution. Bundles are submitted with a tip to incentivize the leader to include them; the Block Engine simulates bundles, selects the most profitable ones, and forwards them to the Jito-enabled leader. Bundles land at the top of a block before standard transactions, giving searchers execution priority.

Open term
Networkbanking-stage

Banking Stage

The critical TPU pipeline stage in which Solana validators execute transactions, update account state, and produce entries that will be packed into a block. Banking stage receives forwarded transactions from the fetch and sigverify stages, acquires account locks via the scheduler, runs transactions through the SVM, and writes results to the accounts database. It is the computational heart of block production and is where compute unit limits, priority fee ordering, and parallel execution all converge.

Open term
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.

Networkbundle

Bundle (Jito)

An atomic group of up to five transactions submitted together through Jito's Block Engine, where either all transactions land in sequence or none do, enabling MEV strategies that depend on guaranteed transaction ordering without risk of partial execution. Bundles are submitted with a tip to incentivize the leader to include them; the Block Engine simulates bundles, selects the most profitable ones, and forwards them to the Jito-enabled leader. Bundles land at the top of a block before standard transactions, giving searchers execution priority.

Open term
Networkblock-engine

Block Engine (Jito)

Jito's off-chain infrastructure component that receives bundles from MEV searchers, simulates them against the current chain state to verify profitability and validity, and forwards the highest-value bundles to the current Jito-enabled leader just before block production. The Block Engine operates as a low-latency relay that continuously tracks the leader schedule and streams winning bundles in real time, acting as a private transaction ordering marketplace sitting between searchers and validators.

Open term
Networkjito

Jito (MEV Infrastructure)

A Solana MEV infrastructure project by Jito Labs that operates a modified validator client (jito-solana), a Block Engine for bundle simulation and routing, and a tip distribution program that collects and distributes MEV tips to staked validators. Jito's client is run by a supermajority of Solana's stake-weighted validators, making its bundle and tip market the de-facto MEV layer for the network. Jito also operates a restaking and liquid staking protocol (JitoSOL) using proceeds from MEV tip redistribution.

Open term
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.

Open term
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.

Open term
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.

Open term
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.

Open term