Red

Private Transaction

A transaction sent directly to the current block producer or through a private relay rather than being broadcast through public RPC nodes, reducing the window for MEV searchers to observe and exploit it before inclusion. On Solana, private transactions can be routed through Jito's Block Engine or via staked connections with direct TPU access. While no transaction is truly private on a public blockchain once confirmed, private submission minimizes the pre-inclusion observation window.

IDprivate-transaction

Lectura rápida

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

A transaction sent directly to the current block producer or through a private relay rather than being broadcast through public RPC nodes, reducing the window for MEV searchers to observe and exploit it before inclusion. On Solana, private transactions can be routed through Jito's Block Engine or via staked connections with direct TPU access. While no transaction is truly private on a public blockchain once confirmed, private submission minimizes the pre-inclusion observation window.

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

Handoff para IA

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

Private Transaction (private-transaction)
Categoría: Red
Definición: A transaction sent directly to the current block producer or through a private relay rather than being broadcast through public RPC nodes, reducing the window for MEV searchers to observe and exploit it before inclusion. On Solana, private transactions can be routed through Jito's Block Engine or via staked connections with direct TPU access. While no transaction is truly private on a public blockchain once confirmed, private submission minimizes the pre-inclusion observation window.
Relacionados: MEV Protection, TPU Client, Block Engine (Jito)
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
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

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

MEV Protection

Mechanisms and tools designed to shield users from harmful MEV extraction such as sandwich attacks and frontrunning. On Solana, MEV protection strategies include using private transaction submission (bypassing public RPCs), setting tight slippage tolerances, routing through MEV-aware aggregators like Jupiter that optimize execution, and submitting transactions via Jito bundles with ordering guarantees. Some wallets and dApps integrate MEV protection by default to improve user outcomes.

Rama

TPU Client

A client library that sends transactions directly to the current leader validator's Transaction Processing Unit (TPU) port over QUIC, bypassing the standard RPC sendTransaction relay for lower latency and higher landing probability. The Solana SDK's TpuClient resolves the current leader from the leader schedule, establishes a QUIC connection, and forwards signed transactions directly. This approach is used by MEV searchers, high-frequency traders, and latency-sensitive applications that need the fastest possible path to block inclusion.

Rama

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.

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.

Red

MEV Protection

Mechanisms and tools designed to shield users from harmful MEV extraction such as sandwich attacks and frontrunning. On Solana, MEV protection strategies include using private transaction submission (bypassing public RPCs), setting tight slippage tolerances, routing through MEV-aware aggregators like Jupiter that optimize execution, and submitting transactions via Jito bundles with ordering guarantees. Some wallets and dApps integrate MEV protection by default to improve user outcomes.

Red

TPU Client

A client library that sends transactions directly to the current leader validator's Transaction Processing Unit (TPU) port over QUIC, bypassing the standard RPC sendTransaction relay for lower latency and higher landing probability. The Solana SDK's TpuClient resolves the current leader from the leader schedule, establishes a QUIC connection, and forwards signed transactions directly. This approach is used by MEV searchers, high-frequency traders, and latency-sensitive applications that need the fastest possible path to block inclusion.

Red

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.

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.

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.

Redtransaction-landing

Transaction Landing

The outcome of a transaction being successfully included and confirmed in a Solana block, as opposed to being dropped, expiring, or failing simulation. Landing probability is influenced by priority fee competitiveness, blockhash freshness (must be within ~150 slots of creation), submission routing (direct to leader vs. RPC rebroadcast), and network congestion on the accounts involved. Developers optimize landing rates by using current-leader TPU endpoints, setting appropriate priority fees, and preflight-checking transactions before submission.

Redtransaction-retry

Transaction Retry / Rebroadcast

The practice of resubmitting a transaction multiple times until it lands or its blockhash expires, necessary because Solana does not guarantee delivery of any single submission and drops can occur at any pipeline stage. By default, Solana RPC nodes rebroadcast submitted transactions periodically, but this is unreliable; production applications implement client-side retry loops that resubmit the same signed transaction (with unchanged signature) at short intervals until confirmation is received or the blockhash expires (roughly 60–90 seconds after creation).

Redvote-transaction

Vote Transaction

A special-purpose transaction submitted by each validator every slot to record its vote on the current fork of the blockchain, serving as the on-chain mechanism for Solana's Tower BFT consensus. Vote transactions are exempt from compute unit limits and priority fee requirements, are processed by a dedicated vote transaction path separate from user transactions, and account for the majority of raw TPS on the network (typically 70–80% of all transactions). Validators pay vote transaction fees from their vote account, which is one reason validator economics require sufficient stake to cover ongoing operating costs.

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.

Redmev-protection

MEV Protection

Mechanisms and tools designed to shield users from harmful MEV extraction such as sandwich attacks and frontrunning. On Solana, MEV protection strategies include using private transaction submission (bypassing public RPCs), setting tight slippage tolerances, routing through MEV-aware aggregators like Jupiter that optimize execution, and submitting transactions via Jito bundles with ordering guarantees. Some wallets and dApps integrate MEV protection by default to improve user outcomes.

Redtpu-client

TPU Client

A client library that sends transactions directly to the current leader validator's Transaction Processing Unit (TPU) port over QUIC, bypassing the standard RPC sendTransaction relay for lower latency and higher landing probability. The Solana SDK's TpuClient resolves the current leader from the leader schedule, establishes a QUIC connection, and forwards signed transactions directly. This approach is used by MEV searchers, high-frequency traders, and latency-sensitive applications that need the fastest possible path to block inclusion.

Redblock-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.

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.

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.

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.

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.