A single byte (255 down to 0) appended to PDA seeds to push the derived address off the Ed25519 curve. find_program_address tries bump=255 first and decrements until finding a valid PDA. The first valid bump found is the canonical bump. Always store and reuse the canonical bump to avoid security issues.
Start with the shortest useful explanation before going deeper.
A single byte (255 down to 0) appended to PDA seeds to push the derived address off the Ed25519 curve. find_program_address tries bump=255 first and decrements until finding a valid PDA. The first valid bump found is the canonical bump. Always store and reuse the canonical bump to avoid security issues.
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.
Place the term inside its Solana layer so the definition is easier to reason about.
Accounts, instructions, PDAs, transactions, and execution flow.
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.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Bump Seed (bump) Category: Programming Model Definition: A single byte (255 down to 0) appended to PDA seeds to push the derived address off the Ed25519 curve. find_program_address tries bump=255 first and decrements until finding a valid PDA. The first valid bump found is the canonical bump. Always store and reuse the canonical bump to avoid security issues. Aliases: Canonical Bump Related: Program Derived Address (PDA), Seeds
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
An account address derived deterministically from a program ID and a set of seeds, with no corresponding private key. PDAs are created by finding a pubkey that does NOT lie on the Ed25519 curve (using a bump seed). Since there's no private key, only the deriving program can sign for the PDA via invoke_signed, making PDAs ideal for program-controlled state.
Byte arrays used as inputs to derive a Program Derived Address. Seeds can be any combination of static strings, user pubkeys, mint addresses, or other identifiers (each seed max 32 bytes, up to 16 seeds). For example, seeds=[b'vault', user.key()] derives a unique vault PDA for each user.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
An account address derived deterministically from a program ID and a set of seeds, with no corresponding private key. PDAs are created by finding a pubkey that does NOT lie on the Ed25519 curve (using a bump seed). Since there's no private key, only the deriving program can sign for the PDA via invoke_signed, making PDAs ideal for program-controlled state.
Byte arrays used as inputs to derive a Program Derived Address. Seeds can be any combination of static strings, user pubkeys, mint addresses, or other identifiers (each seed max 32 bytes, up to 16 seeds). For example, seeds=[b'vault', user.key()] derives a unique vault PDA for each user.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
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.