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.
Empieza por la explicación más corta y útil antes de profundizar.
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.
Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.
Piensa en esto como una de las piezas centrales que tu programa lee, escribe o invoca durante la ejecución.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Accounts, instrucciones, PDAs, transacciones y flujo de ejecución.
Convierte el término de vocabulario en algo operacional para producto e ingeniería.
Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.
Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.
Transaction Mortality (transaction-mortality) Categoría: Modelo de Programación Definición: 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, Transacción
Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.
Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.
El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.
Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.
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.
Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.
Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa 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.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
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.
Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.
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.