Glossary OS

Lectura rápida

Empieza por la explicación más corta y útil antes de profundizar.

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 mental

Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.

Piensa en esto como un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.

Contexto técnico

Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.

Clusters, nodos, actores de MEV, routing y entornos operativos.

Por qué le importa a un builder

Convierte el término de vocabulario en algo operacional para producto e ingeniería.

Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.

Handoff para IA

Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.

Scheduler (scheduler)
Categoría: Red
Definición: 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.
Relacionados: TPU (Unidad de Procesamiento de Transacciones), Parallel Transaction Execution

Glossary Copilot

Haz preguntas de Solana con contexto aterrizado sin salir del glosario.

Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.

Abrir workspace completa del Copilot

Pregunta

Explicar este código

Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.

Haz una pregunta aterrizada en el glosario

El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.

Grafo conceptual

Ve el término como parte de una red, no como una definición aislada.

Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.

Rama

TPU (Unidad de Procesamiento de Transacciones)

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.

TVU (Unidad de Validación de Transacciones)Transacción

Abrir término

Rama

Parallel Transaction Execution

Solana's ability to process multiple transactions simultaneously by analyzing their account access lists and executing non-conflicting transactions in parallel across CPU cores via the Sealevel runtime. Two transactions can run in parallel only if they do not share any writable accounts; transactions sharing a writable account are serialized. This design allows Solana to fully exploit modern multi-core hardware and is a primary contributor to its high throughput.

Sealevel TPS (Transacciones por Segundo)

Abrir término

Siguientes conceptos para explorar

Mantén la cadena de aprendizaje en movimiento en lugar de parar en una sola definición.

Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.

Protocolo Base

TPU (Unidad de Procesamiento de Transacciones)

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.

Abrir término

Red

Parallel Transaction Execution

Solana's ability to process multiple transactions simultaneously by analyzing their account access lists and executing non-conflicting transactions in parallel across CPU cores via the Sealevel runtime. Two transactions can run in parallel only if they do not share any writable accounts; transactions sharing a writable account are serialized. This design allows Solana to fully exploit modern multi-core hardware and is a primary contributor to its high throughput.

Abrir término

Red

Searcher (MEV)

An MEV actor that monitors on-chain state and pending transactions to identify profitable opportunities such as arbitrage, liquidations, or backruns, and submits transaction bundles through Jito's Block Engine to capture that value. Searchers compete on speed and strategy, paying tips to validators for bundle inclusion priority. Searcher operations range from beneficial (keeping markets efficient through arbitrage) to extractive (sandwich attacks that harm regular users).

Abrir término

Red

QUIC Protocol

The UDP-based transport protocol adopted by Solana as its primary transaction submission protocol, replacing raw UDP to provide congestion control, multiplexed streams, and connection-level flow control without TCP's head-of-line blocking. Solana's TPU (Transaction Processing Unit) accepts client transactions over QUIC, allowing the leader to apply back-pressure and drop connections from misbehaving senders. QUIC integration with SWQoS allows leaders to enforce stake-weighted bandwidth limits at the transport layer.

Abrir término

Comúnmente confundido con

Términos cercanos en vocabulario, acrónimo o vecindad conceptual.

Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa de Solana.

Redslashing

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.

Abrir término

Términos relacionados

Sigue los conceptos que realmente le dan contexto a este término.

Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.

Protocolo Basetpu

TPU (Unidad de Procesamiento de Transacciones)

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.

Abrir término

Redparallel-execution

Parallel Transaction Execution

Solana's ability to process multiple transactions simultaneously by analyzing their account access lists and executing non-conflicting transactions in parallel across CPU cores via the Sealevel runtime. Two transactions can run in parallel only if they do not share any writable accounts; transactions sharing a writable account are serialized. This design allows Solana to fully exploit modern multi-core hardware and is a primary contributor to its high throughput.

Abrir término

Más en la categoría

Quédate en la misma capa y sigue construyendo contexto.

Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.

Red

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.

Abrir término

Red

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.

Abrir término

Red

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.

Abrir término

Red

TPS (Transacciones 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.

Abrir término