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.
Comece pela explicação mais curta e útil antes de aprofundar.
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.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como uma das peças centrais que seu programa lê, escreve ou invoca durante a execução.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
Accounts, instruções, PDAs, transações e fluxo de execução.
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.
Assinatura (signature) Categoria: Modelo de Programação Definição: 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. Relacionados: Transação, Par de Chaves, Ed25519
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.
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 pair of a 32-byte Ed25519 private key and its corresponding 32-byte public key. Keypairs are used to sign transactions and derive account addresses. They are stored as 64-byte arrays (private + public concatenated) in JSON files by the Solana CLI. The private key should never be shared or exposed.
The elliptic curve digital signature algorithm used by Solana for all transaction signing. Ed25519 uses Curve25519 and produces 64-byte signatures with 32-byte public keys. Solana also provides an Ed25519 precompile program for on-chain signature verification within program logic.
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.
The runtime struct passed to programs for each account in an instruction: `AccountInfo { key, is_signer, is_writable, lamports, data, owner, executable, rent_epoch }`. In native programs, the entrypoint receives a slice of AccountInfos. Anchor abstracts this with typed account structs but AccountInfo is available via `to_account_info()`.
An account that has provided a valid Ed25519 signature in the current transaction. The runtime enforces the is_signer flag on instruction account metas—if an instruction declares an account as a signer, the transaction must include its signature. Missing signer checks are a common vulnerability in Solana programs.
A pubkey with administrative privileges over a resource—such as the mint authority (can mint tokens), freeze authority (can freeze accounts), upgrade authority (can upgrade a program), or the signer authorized to perform operations on a PDA-controlled account. Authority is a convention, not a runtime concept.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
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 pair of a 32-byte Ed25519 private key and its corresponding 32-byte public key. Keypairs are used to sign transactions and derive account addresses. They are stored as 64-byte arrays (private + public concatenated) in JSON files by the Solana CLI. The private key should never be shared or exposed.
The elliptic curve digital signature algorithm used by Solana for all transaction signing. Ed25519 uses Curve25519 and produces 64-byte signatures with 32-byte public keys. Solana also provides an Ed25519 precompile program for on-chain signature verification within program logic.
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 fundamental data storage unit on Solana. Every piece of state is stored in an account identified by a 32-byte public key. Accounts hold a lamport balance, an owner program, a data byte array (up to 10MB), and an executable flag. Only the owning program can modify an account's data, but anyone can credit lamports to it.
Executable code deployed on-chain, equivalent to a smart contract on other blockchains. Programs are stateless—they store no data themselves but read/write data in separate accounts they own. Programs are compiled to SBF bytecode and loaded via the BPF Loader. Every program has a unique Program ID (its account's public key).
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
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.