OGGlossary OSSolana vocabulary rebuilt for builders.
ENPT-BRES
Programming Model

Nonce Account

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.

IDnonce-account
Plain meaning

Plain meaning

Start with the shortest useful explanation before going deeper.

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.

Mental model

Mental model

Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.

Think of it as one of the core moving pieces your program reads, writes, or invokes at runtime.

Technical context

Technical context

Place the term inside its Solana layer so the definition is easier to reason about.

Accounts, instructions, PDAs, transactions, and execution flow.

Why builders care

Why builders care

Turn the term from vocabulary into something operational for product and engineering work.

This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.

AI handoff

AI handoff

Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.

Nonce Account (nonce-account)
Category: Programming Model
Definition: 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.
Related: Durable Nonce, System Program, Blockhash (Recent)
Glossary Copilot

Ask grounded Solana questions without leaving the glossary.

Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.

Open full Copilot workspace
Explain this code

Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.

Ask a glossary-grounded question

Ask a glossary-grounded question

The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.

Concept graph

See the term as part of a network, not a dead-end definition.

These branches show which concepts this term touches directly and what sits one layer beyond them.

Branch

Durable Nonce

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.

TransactionOffline Signing
Open term
Branch

System Program

The built-in native program (address: 11111111111111111111111111111111) responsible for creating new accounts, transferring SOL between accounts, allocating account data space, and assigning account ownership to programs. It is the only program that can create new accounts and is invoked in nearly every transaction.

ProgramCreate Account
Open term
Branch

Blockhash (Recent)

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.

Open term
Next concepts to explore

Keep the learning chain moving instead of stopping at one definition.

These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.

Network

Durable Nonce

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.

Open term
Programming Model

System Program

The built-in native program (address: 11111111111111111111111111111111) responsible for creating new accounts, transferring SOL between accounts, allocating account data space, and assigning account ownership to programs. It is the only program that can create new accounts and is invoked in nearly every transaction.

Open term
Network

Blockhash (Recent)

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.

Open term
Programming Model

Owner (Account)

The program that has exclusive write access to an account's data and can debit its lamport balance. Every account has an owner field (a program pubkey). The System Program owns all new/wallet accounts. When a program creates a derived account, it typically assigns itself as owner to manage that account's state.

Open term
Commonly confused with

Terms nearby in vocabulary, acronym, or conceptual neighborhood.

These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.

Programming Modelaccount

Account

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.

Open term
Programming Modelaccount-data

Account Data

The byte array stored in an account that holds program-specific state. Data is typically serialized using Borsh and must be explicitly allocated at account creation. The maximum data size is 10MB. Programs are responsible for defining and managing their own data layout, including discriminators for type identification.

Open term
Programming Modelbuffer-account

Buffer Account

A temporary account used during Solana program deployment to hold the program's ELF binary before it is written to the program data account. The deployer creates a buffer account, uploads the compiled SBF binary in chunks via the Upgradeable BPF Loader's Write instruction, and then issues a Deploy or Upgrade instruction that copies the buffer contents to the final program data account. Buffer accounts can be closed after deployment to reclaim rent.

Open term
Related terms

Follow the concepts that give this term its actual context.

Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.

Networkdurable-nonce

Durable Nonce

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.

Open term
Programming Modelsystem-program

System Program

The built-in native program (address: 11111111111111111111111111111111) responsible for creating new accounts, transferring SOL between accounts, allocating account data space, and assigning account ownership to programs. It is the only program that can create new accounts and is invoked in nearly every transaction.

Open term
Networkblockhash

Blockhash (Recent)

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.

Open term
More in category

Stay in the same layer and keep building context.

These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.

Programming Model

Account

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.

Open term
Programming Model

Program

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).

Open term
Programming Model

Instruction

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.

Open term
Programming Model

Transaction

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.

Open term