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.
Comece pela explicação mais curta e útil antes de aprofundar.
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.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nela como o envelope de execução que carrega uma ou mais instruções pelo runtime.
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.
Fica mais útil quando você está navegando por Trilha de Runtime e precisa de vocabulário aterrado dentro de um fluxo real de build.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
Transação (transaction) Categoria: Modelo de Programação Definição: 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. Aliases: TX Relacionados: Instrução, Assinatura, Message
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.
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.
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.
The unsigned payload of a transaction containing: a header (signer/read-only counts), an array of account public keys, a recent blockhash, and compiled instructions. Signers sign the serialized message bytes. In v0 messages, an additional section references address lookup tables.
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.
A transaction format introduced with v0 that supports address lookup tables. Legacy transactions include all pubkeys inline (limited to ~35 accounts); v0 transactions reference ALTs to include up to 256 accounts while staying within the 1,232-byte limit. The version byte (0) precedes the message.
The hard upper limit of 1,400,000 compute units that a single Solana transaction can consume. This cap applies regardless of the SetComputeUnitLimit instruction value — no transaction can request more than 1.4M CU. The default per-instruction budget is 200,000 CU, but multi-instruction transactions share the overall 1.4M cap. Transactions exceeding their CU limit fail with a ComputeBudgetExceeded error.
The simulateTransaction RPC method that dry-runs a transaction against a specified bank state without submitting it to the network or consuming fees. Simulation returns the execution result including logs, compute units consumed, return data, and any error. Developers use simulation to estimate CU usage, debug program errors, and verify transaction correctness before sending. Simulation does not require valid signatures.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
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.
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.
The unsigned payload of a transaction containing: a header (signer/read-only counts), an array of account public keys, a recent blockhash, and compiled instructions. Signers sign the serialized message bytes. In v0 messages, an additional section references address lookup tables.
Use essas trilhas quando quiser sair do lookup isolado e entrar em uma exploração guiada.
Entenda como Solana executa trabalho antes de otimizar ou debugar.
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.
A transaction format introduced with v0 that supports address lookup tables. Legacy transactions include all pubkeys inline (limited to ~35 accounts); v0 transactions reference ALTs to include up to 256 accounts while staying within the 1,232-byte limit. The version byte (0) precedes the message.