On Solana, every transaction requires a fee paid in SOL. This fee has two components: a base fee and an optional priority fee. The priority fee is the additional amount you pay to move your transaction to the front of th...

Adding a priority fee to a Solana transaction requires two instructions from the Compute Budget Program: one to set the compute unit limit and one to set the compute unit price. Both must be added before any other instru...

Use this reference guide to estimate your Solana priority fee before submitting a transaction. The formula is straightforward: Priority Fee (lamports) = ceil(compute_unit_price × compute_unit_limit / 1,000,000). ‍ Kn...

Solana's RPC layer provides built-in methods for querying recent priority fee data, and third-party providers extend this with more sophisticated estimation APIs. Using these tools is essential for any production applica...

Jito Labs operates a modified Solana validator client that introduces a pseudo-mempool called MempoolStream and a bundle execution system. When validators run the Jito client, transaction ordering is influenced not only...

Every Solana transaction is subject to two distinct fee types that serve different purposes and are distributed differently. Understanding both is essential for developers building on Solana and users who want to optimiz...

There is no single correct priority fee for every situation. The optimal fee depends on the current state of the network, the urgency of your transaction, and the accounts it touches. A good strategy adapts dynamically r...

Monitoring real-time priority fee data is essential for developers and traders who want to time their transactions optimally. Fees on Solana can vary by orders of magnitude depending on network load, making live tracking...

Every operation that runs on the Solana runtime has a compute cost measured in compute units (CUs). Arithmetic operations, memory accesses, system calls, and cross-program invocations all consume CUs. Understanding this...