OGGlossary OSSolana vocabulary rebuilt for builders.
ENPT-BRES
Infrastructure

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
Plain meaning

Plain meaning

Start with the shortest useful explanation before going deeper.

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.

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.

RPCs, validators, snapshots, indexing, and network plumbing.

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.

Shredstream Proxy (shredstream-proxy)
Category: Infrastructure
Definition: 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.
Related: Shred, Turbine, Yellowstone gRPC
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

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.

BlockErasure Coding
Open term
Branch

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

Block Propagation
Open term
Branch

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.

Geyser PlugingRPC
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.

Core Protocol

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.

Open term
Core Protocol

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

Open term
Infrastructure

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.

Open term
Infrastructure

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.

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.

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

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.

Core Protocolshred

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.

Open term
Core Protocolturbine

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

Open term
Infrastructureyellowstone

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.

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.

Infrastructure

RPC (Remote Procedure Call)

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.

Open term
Infrastructure

RPC Node

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.

Open term
Infrastructure

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.

Open term
Infrastructure

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.

Open term