The unit used to express compute unit pricing for priority fees on Solana. One lamport equals 1,000,000 micro-lamports. When setting a compute unit price via the Compute Budget Program, the price is specified in micro-lamports per compute unit. The total priority fee is calculated as (compute unit price in micro-lamports * compute units consumed) / 1,000,000, rounded down to lamports.
Comece pela explicação mais curta e útil antes de aprofundar.
The unit used to express compute unit pricing for priority fees on Solana. One lamport equals 1,000,000 micro-lamports. When setting a compute unit price via the Compute Budget Program, the price is specified in micro-lamports per compute unit. The total priority fee is calculated as (compute unit price in micro-lamports * compute units consumed) / 1,000,000, rounded down to lamports.
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.
Micro-Lamport (micro-lamport) Categoria: Modelo de Programação Definição: The unit used to express compute unit pricing for priority fees on Solana. One lamport equals 1,000,000 micro-lamports. When setting a compute unit price via the Compute Budget Program, the price is specified in micro-lamports per compute unit. The total priority fee is calculated as (compute unit price in micro-lamports * compute units consumed) / 1,000,000, rounded down to lamports. Relacionados: Lamport, Compute Unit Price, 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 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.
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.
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 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.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
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.
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.
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.