Infraestructura

Shredstream Proxy

A low-latency relay layer that receives shred feeds from validator-adjacent infrastructure and forwards them into downstream search, trading, or analytics systems without requiring each consumer to maintain its own direct shred connection. Teams use shredstream proxy patterns to normalize transport, centralize access control, and fan out raw block data to internal services that care about block contents before standard RPC surfaces catch up.

IDshredstream-proxy

Lectura rápida

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

A low-latency relay layer that receives shred feeds from validator-adjacent infrastructure and forwards them into downstream search, trading, or analytics systems without requiring each consumer to maintain its own direct shred connection. Teams use shredstream proxy patterns to normalize transport, centralize access control, and fan out raw block data to internal services that care about block contents before standard RPC surfaces catch up.

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.

RPCs, validators, snapshots, indexación y plumbing de red.

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.

Shredstream Proxy (shredstream-proxy)
Categoría: Infraestructura
Definición: A low-latency relay layer that receives shred feeds from validator-adjacent infrastructure and forwards them into downstream search, trading, or analytics systems without requiring each consumer to maintain its own direct shred connection. Teams use shredstream proxy patterns to normalize transport, centralize access control, and fan out raw block data to internal services that care about block contents before standard RPC surfaces catch up.
Relacionados: Shred, Turbine, Yellowstone gRPC
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

Shred

The smallest unit of block data propagated through the network via Turbine. Blocks are split into shreds of up to 1,228 bytes each (fitting in a single UDP packet). Shreds are Reed-Solomon erasure coded—typically 32 data shreds produce 32 recovery shreds—so blocks can be reconstructed even if up to half the shreds are lost.

Rama

Turbine

Solana's block propagation protocol inspired by BitTorrent. Instead of the leader sending a full block to every validator, Turbine organizes validators into a layered tree and propagates shreds through successive tiers. Each node forwards shreds to a small fanout set, reducing the leader's bandwidth requirement from O(n) to O(log n).

Rama

Yellowstone gRPC

An open-source Geyser plugin implementation by Triton One that re-exposes the validator's internal event stream over a gRPC/Protobuf interface, enabling clients to subscribe to filtered streams of account updates, transactions, and slot notifications with sub-millisecond latency from the validator. It has become the de facto streaming standard for Solana MEV bots, high-frequency trading systems, and indexers that require lower latency and richer filtering than WebSocket subscriptions provide.

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

Shred

The smallest unit of block data propagated through the network via Turbine. Blocks are split into shreds of up to 1,228 bytes each (fitting in a single UDP packet). Shreds are Reed-Solomon erasure coded—typically 32 data shreds produce 32 recovery shreds—so blocks can be reconstructed even if up to half the shreds are lost.

Protocolo Base

Turbine

Solana's block propagation protocol inspired by BitTorrent. Instead of the leader sending a full block to every validator, Turbine organizes validators into a layered tree and propagates shreds through successive tiers. Each node forwards shreds to a small fanout set, reducing the leader's bandwidth requirement from O(n) to O(log n).

Infraestructura

Yellowstone gRPC

An open-source Geyser plugin implementation by Triton One that re-exposes the validator's internal event stream over a gRPC/Protobuf interface, enabling clients to subscribe to filtered streams of account updates, transactions, and slot notifications with sub-millisecond latency from the validator. It has become the de facto streaming standard for Solana MEV bots, high-frequency trading systems, and indexers that require lower latency and richer filtering than WebSocket subscriptions provide.

Infraestructura

signatureSubscribe

A Solana WebSocket subscription method that pushes a notification when a specific transaction signature reaches the requested commitment level (processed, confirmed, or finalized). It is the standard way to wait for transaction confirmation without polling, returning the signature status including any error information. The subscription automatically unsubscribes after delivering one notification. Commonly used in dApp frontends to show real-time transaction status updates to users.

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.

Infraestructurasolana-pay

Solana Pay

An open payment standard and SDK that defines URI schemes and protocol flows for requesting SOL or SPL token transfers and for constructing and returning partially-built transactions from merchant backends to user wallets. It comprises two sub-protocols — Transfer Requests (simple static payment URIs) and Transaction Requests (dynamic server-signed transaction fetching) — and enables point-of-sale payments, loyalty programs, and interactive commerce experiences using QR codes or deeplinks.

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 Baseshred

Shred

The smallest unit of block data propagated through the network via Turbine. Blocks are split into shreds of up to 1,228 bytes each (fitting in a single UDP packet). Shreds are Reed-Solomon erasure coded—typically 32 data shreds produce 32 recovery shreds—so blocks can be reconstructed even if up to half the shreds are lost.

Protocolo Baseturbine

Turbine

Solana's block propagation protocol inspired by BitTorrent. Instead of the leader sending a full block to every validator, Turbine organizes validators into a layered tree and propagates shreds through successive tiers. Each node forwards shreds to a small fanout set, reducing the leader's bandwidth requirement from O(n) to O(log n).

Infraestructurayellowstone

Yellowstone gRPC

An open-source Geyser plugin implementation by Triton One that re-exposes the validator's internal event stream over a gRPC/Protobuf interface, enabling clients to subscribe to filtered streams of account updates, transactions, and slot notifications with sub-millisecond latency from the validator. It has become the de facto streaming standard for Solana MEV bots, high-frequency trading systems, and indexers that require lower latency and richer filtering than WebSocket subscriptions provide.

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.

Infraestructura

RPC (Llamada a Procedimiento Remoto)

The JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.

Infraestructura

Nodo RPC

A Solana full node that stores ledger state and serves JSON-RPC and WebSocket requests from clients without participating in consensus or voting. RPC nodes must replay every transaction to maintain an accurate account state database, and high-throughput deployments typically run dedicated RPC nodes with large SSDs, high RAM (256 GB+), and high-bandwidth network connections to handle concurrent client load without impacting validator performance.

Infraestructura

RPC Methods

The enumerated JSON-RPC endpoints exposed by Solana nodes, covering account queries (getAccountInfo, getMultipleAccounts, getProgramAccounts), block and transaction retrieval (getBlock, getTransaction), cluster metadata (getEpochInfo, getSlot, getVersion), and transaction submission (sendTransaction, simulateTransaction). Methods accept a Commitment parameter (processed, confirmed, finalized) to control the recency-vs-safety tradeoff of returned data.

Infraestructura

getAccountInfo

An RPC method that returns the complete on-chain state of a single account identified by its base-58 public key, including its lamport balance, owner program, executable flag, rent epoch, and raw data payload encoded as base64 or base58. It is the most fundamental read primitive in Solana development and is called at the specified commitment level, with the data field being null if the account does not exist.