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.
Start with the shortest useful explanation before going deeper.
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 the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as a building block that connects one definition to the larger Solana system around it.
Place the term inside its Solana layer so the definition is easier to reason about.
RPCs, validators, snapshots, indexing, and network plumbing.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Priority Fee API (priority-fee-api) Category: Infrastructure Definition: 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 Related: Priority Fee, Compute Units (CU), Helius
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
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.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of 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.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
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.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
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.