A native Solana program (address: ComputeBudget111111111111111111111111111111) that allows transactions to configure their compute resource limits. It provides two key instructions: SetComputeUnitLimit (set the max CU a transaction can consume, up to 1.4M) and SetComputeUnitPrice (set the micro-lamport price per CU for priority fees). These instructions must appear before any program instructions in the transaction.
Comece pela explicação mais curta e útil antes de aprofundar.
A native Solana program (address: ComputeBudget111111111111111111111111111111) that allows transactions to configure their compute resource limits. It provides two key instructions: SetComputeUnitLimit (set the max CU a transaction can consume, up to 1.4M) and SetComputeUnitPrice (set the micro-lamport price per CU for priority fees). These instructions must appear before any program instructions in the transaction.
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.
Compute Budget Program (compute-budget-program) Categoria: Modelo de Programação Definição: A native Solana program (address: ComputeBudget111111111111111111111111111111) that allows transactions to configure their compute resource limits. It provides two key instructions: SetComputeUnitLimit (set the max CU a transaction can consume, up to 1.4M) and SetComputeUnitPrice (set the micro-lamport price per CU for priority fees). These instructions must appear before any program instructions in the transaction. Relacionados: Orçamento de Computação, Unidades de Computação (CU), Taxa de Prioridade
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.
The maximum compute units a transaction can consume. Default is 200,000 CU per instruction (max 1.4M CU per transaction). Programs can request specific limits via the ComputeBudgetProgram's SetComputeUnitLimit instruction. Under-requesting CU risks transaction failure; over-requesting wastes priority fee budget.
A measure of computational resources consumed by transaction execution, analogous to gas on Ethereum. Each BPF instruction costs CU; syscalls have predefined CU costs (e.g., SHA-256: 85 CU base + per-byte). Default per-instruction limit is 200,000 CU; max per-transaction is 1,400,000 CU. Priority fee cost = CU price × CU consumed.
An optional additional fee paid on top of the base fee to increase the likelihood that a transaction is processed quickly by the current leader, expressed as a price in micro-lamports per compute unit (CU). The total priority fee equals (compute unit price × compute unit limit) / 1,000,000 lamports. Leaders sort transactions in their queue by fee-per-CU, so setting a competitive priority fee is the primary mechanism for ensuring reliable transaction landing during congestion.
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 maximum compute units a transaction can consume. Default is 200,000 CU per instruction (max 1.4M CU per transaction). Programs can request specific limits via the ComputeBudgetProgram's SetComputeUnitLimit instruction. Under-requesting CU risks transaction failure; over-requesting wastes priority fee budget.
The price per compute unit in micro-lamports that a transaction is willing to pay as a priority fee. Set via the Compute Budget Program's SetComputeUnitPrice instruction. Higher prices increase the likelihood of a transaction being included by the leader during congestion. The effective priority fee equals the compute unit price multiplied by the compute units consumed, converted from micro-lamports to lamports.
A function that derives a PDA by iterating bump seeds from 255 down to 0 until finding a pubkey not on the Ed25519 curve. It returns (pubkey, bump). In Anchor, the #[account(seeds=[...], bump)] constraint calls this automatically. The corresponding create_program_address skips iteration and takes an explicit bump.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
The maximum compute units a transaction can consume. Default is 200,000 CU per instruction (max 1.4M CU per transaction). Programs can request specific limits via the ComputeBudgetProgram's SetComputeUnitLimit instruction. Under-requesting CU risks transaction failure; over-requesting wastes priority fee budget.
A measure of computational resources consumed by transaction execution, analogous to gas on Ethereum. Each BPF instruction costs CU; syscalls have predefined CU costs (e.g., SHA-256: 85 CU base + per-byte). Default per-instruction limit is 200,000 CU; max per-transaction is 1,400,000 CU. Priority fee cost = CU price × CU consumed.
An optional additional fee paid on top of the base fee to increase the likelihood that a transaction is processed quickly by the current leader, expressed as a price in micro-lamports per compute unit (CU). The total priority fee equals (compute unit price × compute unit limit) / 1,000,000 lamports. Leaders sort transactions in their queue by fee-per-CU, so setting a competitive priority fee is the primary mechanism for ensuring reliable transaction landing during congestion.
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.