A System Program instruction that creates a new account with specified space and owner, funding it with enough lamports for rent exemption. Parameters: from (fee payer), to (new account keypair), lamports, space (bytes), and owner (program ID). The new account's data is zero-initialized.
Start with the shortest useful explanation before going deeper.
A System Program instruction that creates a new account with specified space and owner, funding it with enough lamports for rent exemption. Parameters: from (fee payer), to (new account keypair), lamports, space (bytes), and owner (program ID). The new account's data is zero-initialized.
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.
Create Account (create-account) Category: Programming Model Definition: A System Program instruction that creates a new account with specified space and owner, funding it with enough lamports for rent exemption. Parameters: from (fee payer), to (new account keypair), lamports, space (bytes), and owner (program ID). The new account's data is zero-initialized. Related: System Program, Rent, Lamport
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.
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.
A fee mechanism that charges accounts for storing data on-chain. Accounts must maintain a minimum lamport balance proportional to their data size (~6.96 SOL per MB) to be rent-exempt. Since 2022, all new accounts must be rent-exempt at creation. Accounts falling below the threshold are removed during rent collection.
The smallest unit of SOL, named after Leslie Lamport. 1 SOL = 1,000,000,000 (10^9) lamports. All balances and transfers on Solana are denominated in lamports internally. The minimum balance for an account to be rent-exempt is calculated in lamports based on the account's data size.
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 process of reclaiming an account's lamports and marking it for deletion. To close an account: transfer all lamports to a recipient, zero out the data, and (in Anchor) set the discriminator to a closed sentinel. The runtime garbage-collects zero-lamport accounts. Failing to zero data enables revival attacks.
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.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
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.
A fee mechanism that charges accounts for storing data on-chain. Accounts must maintain a minimum lamport balance proportional to their data size (~6.96 SOL per MB) to be rent-exempt. Since 2022, all new accounts must be rent-exempt at creation. Accounts falling below the threshold are removed during rent collection.
The smallest unit of SOL, named after Leslie Lamport. 1 SOL = 1,000,000,000 (10^9) lamports. All balances and transfers on Solana are denominated in lamports internally. The minimum balance for an account to be rent-exempt is calculated in lamports based on the account's data size.
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.