Infrastructure

gRPC

A high-performance, open-source remote procedure call framework from Google that uses HTTP/2 for transport and Protocol Buffers (Protobuf) for binary serialization, offering lower latency, smaller message sizes, and bidirectional streaming compared to JSON-RPC over HTTP/1.1. In Solana infrastructure, gRPC is most prominent as the transport layer for Yellowstone, allowing clients to open long-lived streaming subscriptions with server-side filtering while consuming far less bandwidth than equivalent WebSocket subscriptions.

IDgrpc

Plain meaning

Start with the shortest useful explanation before going deeper.

A high-performance, open-source remote procedure call framework from Google that uses HTTP/2 for transport and Protocol Buffers (Protobuf) for binary serialization, offering lower latency, smaller message sizes, and bidirectional streaming compared to JSON-RPC over HTTP/1.1. In Solana infrastructure, gRPC is most prominent as the transport layer for Yellowstone, allowing clients to open long-lived streaming subscriptions with server-side filtering while consuming far less bandwidth than equivalent WebSocket subscriptions.

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

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

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.

gRPC (grpc)
Category: Infrastructure
Definition: A high-performance, open-source remote procedure call framework from Google that uses HTTP/2 for transport and Protocol Buffers (Protobuf) for binary serialization, offering lower latency, smaller message sizes, and bidirectional streaming compared to JSON-RPC over HTTP/1.1. In Solana infrastructure, gRPC is most prominent as the transport layer for Yellowstone, allowing clients to open long-lived streaming subscriptions with server-side filtering while consuming far less bandwidth than equivalent WebSocket subscriptions.
Related: Yellowstone gRPC, Geyser Plugin
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.

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

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.

Branch

Geyser Plugin

A Solana validator plugin interface (defined in solana-geyser-plugin-interface) that allows external processes to receive a real-time stream of every account update, transaction, slot status change, and block notification directly from the validator's internal processing pipeline via shared-memory callbacks, bypassing the RPC layer entirely. Geyser is the foundation for high-performance indexers, custom databases, and streaming infrastructure like Yellowstone gRPC, because it delivers data at validator speed with zero polling overhead.

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.

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.

Infrastructure

Geyser Plugin

A Solana validator plugin interface (defined in solana-geyser-plugin-interface) that allows external processes to receive a real-time stream of every account update, transaction, slot status change, and block notification directly from the validator's internal processing pipeline via shared-memory callbacks, bypassing the RPC layer entirely. Geyser is the foundation for high-performance indexers, custom databases, and streaming infrastructure like Yellowstone gRPC, because it delivers data at validator speed with zero polling overhead.

Infrastructure

Helius

A Solana-focused infrastructure provider offering dedicated RPC nodes, DAS API access, Geyser-based webhooks, the LaserStream ultra-low-latency streaming product, and enhanced transaction parsing APIs that decode raw instruction data into human-readable event objects. Helius is widely used by developers for its generous free tier, Solana-specific tooling (NFT APIs, token metadata enrichment), and reliable globally distributed RPC endpoints.

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.

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.

Infrastructureget-account-info

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.

Infrastructureget-latest-blockhash

getLatestBlockhash

A Solana RPC method that returns the most recent blockhash along with the last valid block height for that blockhash, providing the two values needed to build and submit a transaction. Every Solana transaction must include a recent blockhash to prevent replay attacks; this method is typically called immediately before signing. The returned lastValidBlockHeight indicates when the blockhash expires, after which unsigned transactions using it will be rejected.

Infrastructureget-multiple-accounts

getMultipleAccounts

A Solana RPC method that fetches the account data for up to 100 public keys in a single request, returning an array of AccountInfo objects in the same order as the input keys. This batched approach is significantly more efficient than calling getAccountInfo repeatedly, reducing round trips and RPC load. It supports the same encoding and commitment parameters as getAccountInfo. Accounts that do not exist return null in the response array.

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.

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.

Infrastructuregeyser

Geyser Plugin

A Solana validator plugin interface (defined in solana-geyser-plugin-interface) that allows external processes to receive a real-time stream of every account update, transaction, slot status change, and block notification directly from the validator's internal processing pipeline via shared-memory callbacks, bypassing the RPC layer entirely. Geyser is the foundation for high-performance indexers, custom databases, and streaming infrastructure like Yellowstone gRPC, because it delivers data at validator speed with zero polling overhead.

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.

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.

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.

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.