Rede

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.

IDbanking-stage

Leitura rápida

Comece pela explicação mais curta e útil antes de aprofundar.

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.

Modelo mental

Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.

Pense nisso como um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.

Contexto técnico

Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.

Clusters, nós, atores de MEV, roteamento e ambientes operacionais.

Por que builders ligam para isso

Transforme o termo de vocabulário em algo operacional para produto e engenharia.

Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.

Handoff para IA

Handoff para IA

Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.

Banking Stage (banking-stage)
Categoria: Rede
Definição: 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.
Relacionados: TPU (Unidade de Processamento de Transações), Scheduler, Transação
Glossary Copilot

Faça perguntas de Solana com contexto aterrado sem sair do glossário.

Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.

Explicar este código

Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.

Faça uma pergunta aterrada no glossário

Faça uma pergunta aterrada no glossário

O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.

Grafo conceitual

Veja o termo como parte de uma rede, não como uma definição sem saída.

Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.

Ramo

TPU (Unidade de Processamento de Transações)

Transaction Processing Unit—the pipeline within a leader validator that ingests, verifies, and executes transactions. The TPU has stages: fetch (receive packets via QUIC), sigverify (verify Ed25519 signatures), banking (execute against current bank state), and broadcast (shred and send via Turbine). Non-leader validators forward transactions to the current leader's TPU.

Ramo

Scheduler

The component within Solana's TPU pipeline responsible for ordering transactions from the banking stage's queues, acquiring account read/write locks, and dispatching transactions to worker threads for execution. The scheduler enforces account conflict serialization (ensuring write-locked accounts are processed by only one thread at a time) while maximizing parallelism across non-conflicting transactions. Solana has iterated on scheduler designs (including the central scheduler introduced in 2024) to improve throughput and reduce lock contention under load.

Ramo

Transação

An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.

Próximos conceitos para explorar

Continue a cadeia de aprendizado em vez de parar em uma única definição.

Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.

Protocolo Base

TPU (Unidade de Processamento de Transações)

Transaction Processing Unit—the pipeline within a leader validator that ingests, verifies, and executes transactions. The TPU has stages: fetch (receive packets via QUIC), sigverify (verify Ed25519 signatures), banking (execute against current bank state), and broadcast (shred and send via Turbine). Non-leader validators forward transactions to the current leader's TPU.

Rede

Scheduler

The component within Solana's TPU pipeline responsible for ordering transactions from the banking stage's queues, acquiring account read/write locks, and dispatching transactions to worker threads for execution. The scheduler enforces account conflict serialization (ensuring write-locked accounts are processed by only one thread at a time) while maximizing parallelism across non-conflicting transactions. Solana has iterated on scheduler designs (including the central scheduler introduced in 2024) to improve throughput and reduce lock contention under load.

Modelo de Programação

Transação

An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.

Rede

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.

Comumente confundido com

Termos próximos em vocabulário, sigla ou vizinhança conceitual.

Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.

Redebundle-simulation

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.

Termos relacionados

Siga os conceitos que realmente dão contexto a este termo.

Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.

Protocolo Basetpu

TPU (Unidade de Processamento de Transações)

Transaction Processing Unit—the pipeline within a leader validator that ingests, verifies, and executes transactions. The TPU has stages: fetch (receive packets via QUIC), sigverify (verify Ed25519 signatures), banking (execute against current bank state), and broadcast (shred and send via Turbine). Non-leader validators forward transactions to the current leader's TPU.

Redescheduler

Scheduler

The component within Solana's TPU pipeline responsible for ordering transactions from the banking stage's queues, acquiring account read/write locks, and dispatching transactions to worker threads for execution. The scheduler enforces account conflict serialization (ensuring write-locked accounts are processed by only one thread at a time) while maximizing parallelism across non-conflicting transactions. Solana has iterated on scheduler designs (including the central scheduler introduced in 2024) to improve throughput and reduce lock contention under load.

Modelo de Programaçãotransaction

Transação

An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.

Mais na categoria

Permaneça na mesma camada e continue construindo contexto.

Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.

Rede

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.

Rede

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.

Rede

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.

Rede

TPS (Transações por Segundo)

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.