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.
Comece pela explicação mais curta e útil antes de aprofundar.
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.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nela como o contêiner de estado que toda app em Solana lê ou escreve.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
Accounts, instruções, PDAs, transações e fluxo de execução.
Transforme o termo de vocabulário em algo operacional para produto e engenharia.
Fica mais útil quando você está navegando por Trilha de Anchor e precisa de vocabulário aterrado dentro de um fluxo real de build.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
Conta (account) Categoria: Modelo de Programação Definição: 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. Relacionados: Chave Pública (Pubkey), Lamport, Aluguel (Rent)
Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.
Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.
O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.
Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.
A 32-byte Ed25519 public key that serves as the unique address for accounts on Solana. Pubkeys are displayed as Base58-encoded strings (e.g., '11111111111111111111111111111111' for the System Program). Every account, program, and PDA is identified by its pubkey.
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.
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.
Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.
Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.
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.
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.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
A 32-byte Ed25519 public key that serves as the unique address for accounts on Solana. Pubkeys are displayed as Base58-encoded strings (e.g., '11111111111111111111111111111111' for the System Program). Every account, program, and PDA is identified by its pubkey.
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.
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.
Use essas trilhas quando quiser sair do lookup isolado e entrar em uma exploração guiada.
Comece pelas abstrações em que a maioria dos times confia para entregar programas com velocidade.
Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.
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.
A transaction format introduced with v0 that supports address lookup tables. Legacy transactions include all pubkeys inline (limited to ~35 accounts); v0 transactions reference ALTs to include up to 256 accounts while staying within the 1,232-byte limit. The version byte (0) precedes the message.