> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/trading/priority-fee.md). # Priority Fee **A small SOL boost that puts your transaction near the front of the queue — not at the front guaranteed.**

Trade Strategy panel — Priority / Bribe / Slippage — Priority sits left of Bribe and Slippage in the Trade Strategy row.

When network activity spikes, Solana validators pick which transactions to include first. Priority Fee is the extra SOL you offer on top of the base cost to improve your odds. It doesn't guarantee a fill — it tilts the probability. The field lives in **Trade Strategy** alongside Bribe and Slippage. During review the value shown was `0.0002 SOL`. {% hint style="success" %} **Tune Priority with intent** A tuned Priority Fee is the difference between catching a launch and watching it run without you. Worth 10 seconds before the next session. {% endhint %} ## What Priority Actually Does * Adds SOL on top of the base transaction fee. * Signals to validators that your transaction is worth prioritizing. * Applies per-transaction — every Buy / Sell uses the current value until you change it. * Inherited from Speed Presets (Slow / Fast / Turbo) when you switch a preset. It does **not** guarantee that the trade will succeed, fill at the expected price, or avoid price movement. ## When to Review It Before: * Trading a fast-moving token. * Using **Quick Buy** or other one-click execution flows. * Trading during heavy market activity (mints, listings, news). * Increasing Slippage or Bribe at the same time — the three settings interact. A fast environment that warrants Turbo on Priority usually warrants matching tweaks to Bribe and Slippage too. ## Cost Risk Higher Priority increases the SOL spent per transaction, whether or not the trade succeeds. A `0.05 SOL` priority on a `0.1 SOL` test trade is a 50% premium — pay it deliberately. * Failed transactions still consume the Priority Fee. * Aggressive priority on low-value trades wipes profit. * Stacking Priority + Bribe + High Slippage on a small position can cost more than the position itself. For deeper coverage, see [Risk of Fast Execution Settings](/graphdex-docs/trading/risk-of-fast-execution-settings.md) and [Execution Risks](/graphdex-docs/trading/execution-risks.md). ## More to Explore

		Cover image
Validator Bribe	The other speed lever in Trade Strategy.	/files/aVYqE79eKRLE9y13C7Y5
Slippage	Price tolerance — pair it with Priority on volatile pairs.	/files/aVYqE79eKRLE9y13C7Y5
Presets & Quick Suggestions	Save Priority + Bribe + Slippage as a single profile.	/files/LHWphZ9IlEe2zGQmxOwz

{% hint style="info" %} Three speed levers — Priority, Bribe, Slippage — live in the same row. Tune them as a set, not individually. See [Trading Settings Overview](/graphdex-docs/trading/trading-settings-overview.md) for the full picture. {% endhint %} ## FAQs

Does a higher Priority Fee guarantee my transaction lands first?

No — it improves probability, not certainty. Other transactions can outbid yours, and validator order isn't strictly fee-sorted.

What happens to Priority Fee if my trade fails?

You still pay it. The Fee compensates validators for processing the attempt regardless of outcome.

Should Priority match the Turbo preset on every trade?

Only when speed is the bottleneck. Routine trades on liquid pairs don't need Turbo — start at Fast and escalate when you see actual inclusion delays.

How does Priority differ from Bribe?

Priority is the standard validator tip. Bribe is a separate execution incentive layered on top. Both raise cost; both improve inclusion odds in different ways.

Where is the current Priority value displayed?

In the Trade Strategy row of Trading Settings, under the \`Priority\` label, in SOL. Change it inline and the next order picks up the new value.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://graphdex-1.gitbook.io/graphdex-docs/trading/priority-fee.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.