Infraestrutura

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.

IDsignature-subscribe

Leitura rápida

Comece pela explicação mais curta e útil antes de aprofundar.

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.

Modelo mental

Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.

Pense nisso como um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.

Contexto técnico

Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.

RPCs, validators, snapshots, indexação e plumbing da rede.

Por que builders ligam para isso

Transforme o termo de vocabulário em algo operacional para produto e engenharia.

Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.

Handoff para IA

Handoff para IA

Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.

signatureSubscribe (signature-subscribe)
Categoria: Infraestrutura
Definição: 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.
Relacionados: Assinaturas WebSocket, Assinatura, Níveis de Compromisso
Glossary Copilot

Faça perguntas de Solana com contexto aterrado sem sair do glossário.

Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.

Explicar este código

Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.

Faça uma pergunta aterrada no glossário

Faça uma pergunta aterrada no glossário

O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.

Grafo conceitual

Veja o termo como parte de uma rede, não como uma definição sem saída.

Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.

Ramo

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

Ramo

Assinatura

A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.

Ramo

Níveis de Compromisso

The three transaction confirmation tiers exposed by Solana RPC: 'processed' (transaction executed by leader, not yet voted on), 'confirmed' (optimistic confirmation—66.7%+ stake voted, ~400ms), and 'finalized' (rooted—31+ confirmations, ~12-13s). Applications choose the level based on their security vs. latency requirements.

Próximos conceitos para explorar

Continue a cadeia de aprendizado em vez de parar em uma única definição.

Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.

Infraestrutura

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

Modelo de Programação

Assinatura

A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.

Protocolo Base

Níveis de Compromisso

The three transaction confirmation tiers exposed by Solana RPC: 'processed' (transaction executed by leader, not yet voted on), 'confirmed' (optimistic confirmation—66.7%+ stake voted, ~400ms), and 'finalized' (rooted—31+ confirmations, ~12-13s). Applications choose the level based on their security vs. latency requirements.

Infraestrutura

Solana Actions

A protocol specification that standardizes how web servers expose signable Solana transactions and messages via HTTPS endpoints, enabling any URL to become an interactive blockchain entry point. Actions use a GET/POST handshake similar to Solana Pay Transaction Requests but are generalized beyond payments to support arbitrary on-chain operations (voting, staking, DeFi interactions), and serve as the server-side counterpart to Blinks, which render Actions as embeddable UI components.

Termos relacionados

Siga os conceitos que realmente dão contexto a este termo.

Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.

Infraestruturawebsocket

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

Modelo de Programaçãosignature

Assinatura

A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.

Protocolo Basecommitment-levels

Níveis de Compromisso

The three transaction confirmation tiers exposed by Solana RPC: 'processed' (transaction executed by leader, not yet voted on), 'confirmed' (optimistic confirmation—66.7%+ stake voted, ~400ms), and 'finalized' (rooted—31+ confirmations, ~12-13s). Applications choose the level based on their security vs. latency requirements.

Mais na categoria

Permaneça na mesma camada e continue construindo contexto.

Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.

Infraestrutura

RPC (Chamada de Procedimento 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.

Infraestrutura

Nó 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.

Infraestrutura

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.

Infraestrutura

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.