Infraestructura

Suscripciones WebSocket

A persistent bidirectional connection to a Solana RPC node's WebSocket endpoint (typically on port 8900) that allows clients to receive real-time push notifications when on-chain state changes, rather than polling via HTTP. The subscription model supports account changes, program account changes, slot updates, root changes, signature confirmations, and log emission, each returning a subscription ID used to later unsubscribe.

IDwebsocket

Lectura rápida

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

A persistent bidirectional connection to a Solana RPC node's WebSocket endpoint (typically on port 8900) that allows clients to receive real-time push notifications when on-chain state changes, rather than polling via HTTP. The subscription model supports account changes, program account changes, slot updates, root changes, signature confirmations, and log emission, each returning a subscription ID used to later unsubscribe.

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.

Suscripciones WebSocket (websocket)
Categoría: Infraestructura
Definición: A persistent bidirectional connection to a Solana RPC node's WebSocket endpoint (typically on port 8900) that allows clients to receive real-time push notifications when on-chain state changes, rather than polling via HTTP. The subscription model supports account changes, program account changes, slot updates, root changes, signature confirmations, and log emission, each returning a subscription ID used to later unsubscribe.
Relacionados: RPC (Llamada a Procedimiento Remoto), accountSubscribe, logsSubscribe
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

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.

Rama

accountSubscribe

A WebSocket subscription method that pushes a notification to the client every time the data or lamport balance of a specified account changes, delivering the updated AccountInfo payload at the configured commitment level. It is commonly used by UIs to reactively update token balances, NFT ownership, or program state without polling, and each subscription is referenced by a numeric subscription ID returned upon successful registration.

Rama

logsSubscribe

A WebSocket subscription method that streams transaction log messages in real time as transactions are processed by the cluster, filterable by 'all' (every transaction), 'allWithVotes' (including vote transactions), or a specific program public key. It is the lowest-latency way for bots and monitoring systems to react to on-chain events emitted via Solana's msg! macro or Anchor's emit! macro without running a full validator or Geyser plugin.

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.

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

accountSubscribe

A WebSocket subscription method that pushes a notification to the client every time the data or lamport balance of a specified account changes, delivering the updated AccountInfo payload at the configured commitment level. It is commonly used by UIs to reactively update token balances, NFT ownership, or program state without polling, and each subscription is referenced by a numeric subscription ID returned upon successful registration.

Infraestructura

logsSubscribe

A WebSocket subscription method that streams transaction log messages in real time as transactions are processed by the cluster, filterable by 'all' (every transaction), 'allWithVotes' (including vote transactions), or a specific program public key. It is the lowest-latency way for bots and monitoring systems to react to on-chain events emitted via Solana's msg! macro or Anchor's emit! macro without running a full validator or Geyser plugin.

Infraestructura

Transaction Request (Solana Pay)

A Solana Pay protocol flow in which a QR code or link encodes an HTTPS URL; when scanned, the wallet performs a GET request to discover metadata (label, icon) and then a POST request with the user's public key, receiving a base64-encoded partially-signed transaction that the wallet can inspect, sign, and submit. This dynamic model enables programmable commerce flows such as NFT minting, coupon redemption, and multi-step checkout because the merchant server constructs the transaction at request time rather than encoding it statically.

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.

Infraestructurarpc

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.

Infraestructuraaccount-subscribe

accountSubscribe

A WebSocket subscription method that pushes a notification to the client every time the data or lamport balance of a specified account changes, delivering the updated AccountInfo payload at the configured commitment level. It is commonly used by UIs to reactively update token balances, NFT ownership, or program state without polling, and each subscription is referenced by a numeric subscription ID returned upon successful registration.

Infraestructuralogs-subscribe

logsSubscribe

A WebSocket subscription method that streams transaction log messages in real time as transactions are processed by the cluster, filterable by 'all' (every transaction), 'allWithVotes' (including vote transactions), or a specific program public key. It is the lowest-latency way for bots and monitoring systems to react to on-chain events emitted via Solana's msg! macro or Anchor's emit! macro without running a full validator or Geyser plugin.

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.