The property where performing an operation multiple times produces the same result as performing it once. Critical in blockchain development because transactions can be submitted multiple times (e.g., during retries). Solana mitigates duplicate execution via recent blockhash expiry (~60-90 seconds) and transaction deduplication. Designing idempotent instructions prevents double-spending.
Empieza por la explicación más corta y útil antes de profundizar.
The property where performing an operation multiple times produces the same result as performing it once. Critical in blockchain development because transactions can be submitted multiple times (e.g., during retries). Solana mitigates duplicate execution via recent blockhash expiry (~60-90 seconds) and transaction deduplication. Designing idempotent instructions prevents double-spending.
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 un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Serialización, memoria, estructuras de datos y bases de ingeniería.
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.
Idempotency (idempotency) Categoría: Fundamentos de Programación Definición: The property where performing an operation multiple times produces the same result as performing it once. Critical in blockchain development because transactions can be submitted multiple times (e.g., during retries). Solana mitigates duplicate execution via recent blockhash expiry (~60-90 seconds) and transaction deduplication. Designing idempotent instructions prevents double-spending. Relacionados: Transacción, Nonce Account
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.
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 special account managed by the System Program that stores a durable nonce value, enabling transactions with extended or indefinite lifetimes. Normally, transactions reference a recent blockhash and expire after ~60-90 seconds. Nonce accounts replace the blockhash with a stored nonce that remains valid until explicitly advanced, enabling offline signing workflows, scheduled transactions, and custodial operations where signing and submission happen at different times.
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.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
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 special account managed by the System Program that stores a durable nonce value, enabling transactions with extended or indefinite lifetimes. Normally, transactions reference a recent blockhash and expire after ~60-90 seconds. Nonce accounts replace the blockhash with a stored nonce that remains valid until explicitly advanced, enabling offline signing workflows, scheduled transactions, and custodial operations where signing and submission happen at different times.
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.
A systems programming language emphasizing memory safety, zero-cost abstractions, and concurrency without a garbage collector. Rust uses an ownership model with borrow checking at compile time to prevent data races and null pointer bugs. It is the primary language for Solana program development (via Anchor or native solana-program crate) and the Agave validator client.
A statically typed superset of JavaScript that compiles to plain JavaScript. TypeScript adds type annotations, interfaces, generics, and enums to catch errors at compile time. It is the standard language for Solana client-side development—wallet adapters, dApp frontends, test suites, and SDK interactions (web3.js, Anchor client) are typically written in TypeScript.
The ubiquitous scripting language for web development, running in browsers and Node.js. JavaScript is dynamically typed and event-driven. Most Solana dApp frontends and scripts use JavaScript/TypeScript with libraries like @solana/web3.js. Node.js enables server-side JS for backend services, indexers, and bot development.
A JavaScript runtime built on Chrome's V8 engine that enables server-side JavaScript execution. Node.js uses an event-driven, non-blocking I/O model. In the Solana ecosystem, Node.js is used for: running Anchor tests (Mocha/Jest), backend services, transaction bots, indexers, and CLI tools. npm/yarn/pnpm manage JavaScript package dependencies.