An account flag indicating the account contains deployed program bytecode. Once marked executable, an account cannot be modified except through the upgrade mechanism. The data field contains the SBF ELF binary (or for upgradeable programs, a pointer to the program data account).
Start with the shortest useful explanation before going deeper.
An account flag indicating the account contains deployed program bytecode. Once marked executable, an account cannot be modified except through the upgrade mechanism. The data field contains the SBF ELF binary (or for upgradeable programs, a pointer to the program data account).
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.
Executable Account (executable) Category: Programming Model Definition: An account flag indicating the account contains deployed program bytecode. Once marked executable, an account cannot be modified except through the upgrade mechanism. The data field contains the SBF ELF binary (or for upgradeable programs, a pointer to the program data account). Related: Program, BPF Loader, Upgradeable BPF Loader
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.
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 built-in program that loads and executes SBF programs. Solana has multiple loader versions: the deprecated BPF Loader (immutable programs), BPF Loader 2 (deprecated), and the current Upgradeable BPF Loader (BPFLoaderUpgradeable) that supports program upgrades. The loader verifies bytecode, manages deployment, and sets the executable flag.
The current BPF Loader (BPFLoaderUpgradeab1e111...) that supports deploying and upgrading programs. It creates three accounts: the program account (thin proxy with executable flag), the program data account (holds the actual ELF bytecode), and records the upgrade authority. Programs can be made immutable by setting the authority to None.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.
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.
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.
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.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
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 built-in program that loads and executes SBF programs. Solana has multiple loader versions: the deprecated BPF Loader (immutable programs), BPF Loader 2 (deprecated), and the current Upgradeable BPF Loader (BPFLoaderUpgradeable) that supports program upgrades. The loader verifies bytecode, manages deployment, and sets the executable flag.
The current BPF Loader (BPFLoaderUpgradeab1e111...) that supports deploying and upgrading programs. It creates three accounts: the program account (thin proxy with executable flag), the program data account (holds the actual ELF bytecode), and records the upgrade authority. Programs can be made immutable by setting the authority to None.
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.