The limited lifespan of a Solana transaction determined by its referenced blockhash. A transaction's blockhash must correspond to a block within the last 150 slots (~60-90 seconds) or the transaction is rejected as expired. This mechanism prevents replay attacks and bounds the time validators must track transaction deduplication. Durable nonces bypass mortality for use cases requiring long-lived transactions.
Comece pela explicação mais curta e útil antes de aprofundar.
The limited lifespan of a Solana transaction determined by its referenced blockhash. A transaction's blockhash must correspond to a block within the last 150 slots (~60-90 seconds) or the transaction is rejected as expired. This mechanism prevents replay attacks and bounds the time validators must track transaction deduplication. Durable nonces bypass mortality for use cases requiring long-lived transactions.
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.
Transaction Mortality (transaction-mortality) Categoria: Modelo de Programação Definição: The limited lifespan of a Solana transaction determined by its referenced blockhash. A transaction's blockhash must correspond to a block within the last 150 slots (~60-90 seconds) or the transaction is rejected as expired. This mechanism prevents replay attacks and bounds the time validators must track transaction deduplication. Durable nonces bypass mortality for use cases requiring long-lived transactions. Relacionados: Blockhash (Recent), Durable Nonce, Transação
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 32-byte hash derived from the bank's state at a given slot, included in every Solana transaction to prove the transaction was created recently and to prevent replay attacks. A blockhash remains valid for approximately 150 slots (~60–90 seconds at normal slot times); transactions submitted with an expired blockhash are rejected outright. Clients must fetch a fresh blockhash before signing and ideally reuse it for as short a window as possible to maximize landing probability.
A mechanism that replaces the short-lived recent blockhash in a transaction with a nonce value stored in a dedicated on-chain nonce account, allowing the transaction to remain valid indefinitely until it is used or the nonce is advanced. The nonce account stores the current nonce hash and an authority; the first instruction of any durable-nonce transaction must be AdvanceNonceAccount, which updates the nonce and invalidates the old one. Durable nonces are essential for workflows requiring offline signing, hardware security modules, or multi-party approval over extended time periods.
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.
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 first signature in a transaction, which uniquely identifies it on the network. Since each transaction has a unique combination of signers and a recent blockhash, the first signer's Ed25519 signature over the transaction message serves as a globally unique identifier. Transaction IDs are displayed as Base58-encoded 64-byte strings and used for lookups via getTransaction and getSignatureStatuses.
The broader developer workflow of dry-running a Solana transaction before broadcast to inspect logs, catch runtime failures, estimate compute usage, and verify account assumptions. Transaction simulation can happen through the simulateTransaction RPC method, preflight checks inside sendTransaction, or specialized bundle and bot pipelines that repeatedly simulate against fresh state before deciding to submit.
The maximum serialized size of a Solana transaction: 1,232 bytes, matching the IPv6 minimum MTU to ensure single-packet transmission. This limit constrains the number of accounts, instructions, and data per transaction. Address lookup tables (v0 transactions) help fit more accounts within this limit.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
A 32-byte hash derived from the bank's state at a given slot, included in every Solana transaction to prove the transaction was created recently and to prevent replay attacks. A blockhash remains valid for approximately 150 slots (~60–90 seconds at normal slot times); transactions submitted with an expired blockhash are rejected outright. Clients must fetch a fresh blockhash before signing and ideally reuse it for as short a window as possible to maximize landing probability.
A mechanism that replaces the short-lived recent blockhash in a transaction with a nonce value stored in a dedicated on-chain nonce account, allowing the transaction to remain valid indefinitely until it is used or the nonce is advanced. The nonce account stores the current nonce hash and an authority; the first instruction of any durable-nonce transaction must be AdvanceNonceAccount, which updates the nonce and invalidates the old one. Durable nonces are essential for workflows requiring offline signing, hardware security modules, or multi-party approval over extended time periods.
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.
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.