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.
Comece pela explicação mais curta e útil antes de aprofundar.
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.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como uma das peças centrais que seu programa lê, escreve ou invoca durante a execução.
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.
Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
Upgradeable BPF Loader (upgradeable-loader) Categoria: Modelo de Programação Definição: 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. Aliases: BPFLoaderUpgradeable Relacionados: BPF Loader, Program Data Account, Upgrade Authority
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 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 account that stores the actual SBF ELF bytecode for an upgradeable program. It is separate from the program's main account (which just points to the program data). This separation allows the bytecode to be swapped during upgrades while the program ID stays the same. The program data account also stores the upgrade authority pubkey.
The pubkey authorized to upgrade a program's bytecode via the Upgradeable BPF Loader. Only the upgrade authority can deploy new bytecode to the program data account. Setting the upgrade authority to None makes the program immutable. Multisig (e.g., Squads) is commonly used to manage upgrade authority for production programs.
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.
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.
A built-in program responsible for deploying, loading, and executing on-chain programs by interpreting their binary encoding. Solana has multiple loaders: the original BPF Loader (deprecated, immutable programs), BPF Loader 2 (deprecated), and the current Upgradeable BPF Loader that supports program upgrades and manages the program/program-data account split.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
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 account that stores the actual SBF ELF bytecode for an upgradeable program. It is separate from the program's main account (which just points to the program data). This separation allows the bytecode to be swapped during upgrades while the program ID stays the same. The program data account also stores the upgrade authority pubkey.
The pubkey authorized to upgrade a program's bytecode via the Upgradeable BPF Loader. Only the upgrade authority can deploy new bytecode to the program data account. Setting the upgrade authority to None makes the program immutable. Multisig (e.g., Squads) is commonly used to manage upgrade authority for production programs.
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.
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.