Solana Priority Fees Best Practices

Optimizing your Solana priority fee strategy requires balancing speed, reliability, and cost. Following industry best practices ensures your transactions land on-chain consistently without overpaying during normal conditions or underpaying during peak demand.

1. Always set both CU limit and CU price. Setting only the compute unit price without an accurate CU limit means you default to the 200,000 CU limit. Simulate first, then set an accurate limit with a small buffer to improve your priority score and reduce unnecessary fees.

2. Use dynamic fee estimation, not static values. Hardcoding a fixed compute unit price will result in consistent failures during network congestion and overpayment during quiet periods.

3. Match fee tier to transaction urgency. Use the Low tier (25th percentile) for non-urgent batch operations. Use Medium (50th) for regular app transactions. Use High or VeryHigh (75th–95th percentile) for time-sensitive trades and competitive mints.

Monitor your transaction landing rate over time. If you see frequent timeouts or failures, increase your priority fee tier.

4. Use localized fee data. Pass the specific writable account keys your transaction touches to getRecentPrioritizationFees rather than querying global network data.

5. Implement retry logic with fee escalation. For critical transactions, implement automatic retry with a progressively higher fee if the initial attempt does not land within a target time window.