An RPC API (primarily Helius's getPriorityFeeEstimate) that calculates optimal priority fee recommendations based on real-time network congestion and historical fee data. Priority fees are priced in microlamports per compute unit. The API returns tiered estimates (low, medium, high, very high) to help developers balance cost and confirmation speed.
Comece pela explicação mais curta e útil antes de aprofundar.
An RPC API (primarily Helius's getPriorityFeeEstimate) that calculates optimal priority fee recommendations based on real-time network congestion and historical fee data. Priority fees are priced in microlamports per compute unit. The API returns tiered estimates (low, medium, high, very high) to help developers balance cost and confirmation speed.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
RPCs, validators, snapshots, indexação e plumbing da rede.
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.
Priority Fee API (priority-fee-api) Categoria: Infraestrutura Definição: An RPC API (primarily Helius's getPriorityFeeEstimate) that calculates optimal priority fee recommendations based on real-time network congestion and historical fee data. Priority fees are priced in microlamports per compute unit. The API returns tiered estimates (low, medium, high, very high) to help developers balance cost and confirmation speed. Aliases: getPriorityFeeEstimate Relacionados: Taxa de Prioridade, Unidades de Computação (CU), Helius
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.
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.
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.
A Solana-focused infrastructure provider offering dedicated RPC nodes, DAS API access, Geyser-based webhooks, the LaserStream ultra-low-latency streaming product, and enhanced transaction parsing APIs that decode raw instruction data into human-readable event objects. Helius is widely used by developers for its generous free tier, Solana-specific tooling (NFT APIs, token metadata enrichment), and reliable globally distributed RPC endpoints.
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 unified RPC API specification, originated by Metaplex and adopted by major RPC providers, that provides indexed, queryable access to Solana digital assets including regular NFTs, compressed NFTs (cNFTs), and fungible tokens through methods like getAsset, getAssetsByOwner, getAssetsByGroup, and searchAssets. DAS abstracts away the complexity of reading raw Metaplex account data and reconstructing compressed NFT state from concurrent Merkle trees, making it the standard NFT data layer for wallets and marketplaces.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
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.
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.
A Solana-focused infrastructure provider offering dedicated RPC nodes, DAS API access, Geyser-based webhooks, the LaserStream ultra-low-latency streaming product, and enhanced transaction parsing APIs that decode raw instruction data into human-readable event objects. Helius is widely used by developers for its generous free tier, Solana-specific tooling (NFT APIs, token metadata enrichment), and reliable globally distributed RPC endpoints.
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 JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.
A Solana full node that stores ledger state and serves JSON-RPC and WebSocket requests from clients without participating in consensus or voting. RPC nodes must replay every transaction to maintain an accurate account state database, and high-throughput deployments typically run dedicated RPC nodes with large SSDs, high RAM (256 GB+), and high-bandwidth network connections to handle concurrent client load without impacting validator performance.
The enumerated JSON-RPC endpoints exposed by Solana nodes, covering account queries (getAccountInfo, getMultipleAccounts, getProgramAccounts), block and transaction retrieval (getBlock, getTransaction), cluster metadata (getEpochInfo, getSlot, getVersion), and transaction submission (sendTransaction, simulateTransaction). Methods accept a Commitment parameter (processed, confirmed, finalized) to control the recency-vs-safety tradeoff of returned data.
An RPC method that returns the complete on-chain state of a single account identified by its base-58 public key, including its lamport balance, owner program, executable flag, rent epoch, and raw data payload encoded as base64 or base58. It is the most fundamental read primitive in Solana development and is called at the specified commitment level, with the data field being null if the account does not exist.