Solana Base Fee vs Priority Fee Explained

Every Solana transaction has two potential fee components: a mandatory base fee and an optional priority fee. Understanding both is essential for anyone building on Solana or using it frequently. The base fee compensates validators for the cryptographic work of verifying transaction signatures. The priority fee increases the probability that validators will schedule your transaction ahead of competing ones.

The base fee is calculated at 5,000 lamports per signature on a transaction. Most standard transactions have a single signature, resulting in a base fee of 0.000005 SOL. Transactions with multiple signers — such as multi-sig wallets or certain program invocations — incur proportionally higher base fees. This portion of the fee is split 50% burned (permanently removed from SOL supply) and 50% distributed to the current block's validator.

The base fee is non-negotiable and always applies. The priority fee is optional — but during peak demand events, omitting it can result in your transaction being delayed or dropped.

The priority fee is expressed in micro-lamports per compute unit. You set both a compute unit price (micro-lamports per CU) and a compute unit limit for your transaction. The total priority fee is: ceil(compute_unit_price × compute_unit_limit ÷ 1,000,000) lamports. One hundred percent of the priority fee goes directly to the validator processing your transaction — none is burned.

Setting priority fees correctly requires understanding your transaction's compute budget. Use ComputeBudgetInstruction.setComputeUnitPrice() and setComputeUnitLimit() in your transaction building code. For most routine transfers, a priority fee of 1 micro-lamport per CU is sufficient. For time-sensitive DeFi operations, 10,000–100,000 micro-lamports per CU may be warranted during congested periods.