An RPC method that returns a paginated, reverse-chronological list of transaction signatures that reference a given account address, along with each transaction's slot, block time, memo, and confirmation status. It is the standard way to walk the transaction history of a wallet or program account and accepts before and until signature parameters for cursor-based pagination through up to 1,000 signatures per call.
Comece pela explicação mais curta e útil antes de aprofundar.
An RPC method that returns a paginated, reverse-chronological list of transaction signatures that reference a given account address, along with each transaction's slot, block time, memo, and confirmation status. It is the standard way to walk the transaction history of a wallet or program account and accepts before and until signature parameters for cursor-based pagination through up to 1,000 signatures per call.
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.
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.
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.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
getSignaturesForAddress (get-signatures-for-address) Categoria: Infraestrutura Definição: An RPC method that returns a paginated, reverse-chronological list of transaction signatures that reference a given account address, along with each transaction's slot, block time, memo, and confirmation status. It is the standard way to walk the transaction history of a wallet or program account and accepts before and until signature parameters for cursor-based pagination through up to 1,000 signatures per call. Relacionados: RPC Methods, Transação, Assinatura
Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.
Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.
O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.
Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.
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.
An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.
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.
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.
Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.
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.
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.
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.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
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.
An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.
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.
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.
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.
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.
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.
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.