> 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/slippage.md).

# Slippage

**The price you wanted minus the price you got — measured in percent.**

<div align="center"><figure><img src="/files/aVYqE79eKRLE9y13C7Y5" alt="Trade Strategy panel — Priority / Bribe / Slippage"><figcaption><p>Slippage sits next to Priority and Bribe in the Trade Strategy row.</p></figcaption></figure></div>

Solana token prices can move quickly, especially for newly launched or low-liquidity tokens. Slippage is the tolerance you give the engine — set too low, the trade fails because the market drifted before execution; set too high, the trade fills at a much worse price than expected.

Slippage is a setting, not a recommendation. Review it before every trading session and adjust to the token, liquidity, and volatility you're actually willing to wear.

{% hint style="success" %}
**Tune it once per session**

The first thing experienced traders touch when a session opens — slippage by token tier, then Priority, then Bribe.
{% endhint %}

## Where Slippage Lives

You'll find Slippage in the **Trade Strategy** row of Trading Settings — the same row as Priority and Bribe. The field is a percentage; during review the default value shown was `20%`.

* Editable per session.
* Applied to every Buy / Sell submission until you change it.
* Inherited from Speed Presets (Slow / Fast / Turbo) when you switch a preset.

## How to Pick a Value

* **Low slippage (1–5%)** — stricter price control, suitable for liquid markets and limit-style entries.
* **Medium (5–15%)** — balanced default for typical Solana tokens.
* **High (15%+)** — only when you understand the cost of worse execution. Common on newly launched, low-liquidity, or fast-moving tokens.

Pay extra attention before using **Quick Buy** or other fast-execution flows — they submit instantly without a second confirmation, so the slippage you set is the slippage you get.

## Slippage Risk

High slippage can make a trade fill at a price far away from the price you saw in the terminal. GraphDex cannot guarantee execution price — the engine respects whatever tolerance you set.

* **Failed trades.** Too low? The market drifted; transaction reverts.
* **Worse fills.** Too high? You accept whatever price the pool offers.
* **MEV exposure.** Aggressive slippage on illiquid pairs makes you a sandwiching target.

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

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/cvGJYoD9UstDDnIsicyY"><strong>Priority Fee</strong></a></td><td>The SOL boost that improves inclusion.</td><td><a href="/files/aVYqE79eKRLE9y13C7Y5">/files/aVYqE79eKRLE9y13C7Y5</a></td></tr><tr><td><a href="/pages/IkJfkROgkbxwBDSMXZYT"><strong>Validator Bribe</strong></a></td><td>Extra incentive for execution speed.</td><td><a href="/files/aVYqE79eKRLE9y13C7Y5">/files/aVYqE79eKRLE9y13C7Y5</a></td></tr><tr><td><a href="/pages/yusGAAjugh8EIaKFi5k6"><strong>Presets &#x26; Quick Suggestions</strong></a></td><td>Bundle slippage with priority and bribe in a reusable profile.</td><td><a href="/files/LHWphZ9IlEe2zGQmxOwz">/files/LHWphZ9IlEe2zGQmxOwz</a></td></tr></tbody></table>

{% hint style="info" %}
Slippage rarely lives in isolation — tune it alongside [Priority Fee](/graphdex-docs/trading/priority-fee.md) and [Validator Bribe](/graphdex-docs/trading/validator-bribe.md) for the full execution profile.
{% endhint %}

## FAQs

<details>

<summary>What slippage should I use on a brand-new token?</summary>

Newly launched tokens are extremely volatile. Many traders start at 15–25% and step it down as liquidity stabilizes. There is no universally correct value — always check the pool's depth first.

</details>

<details>

<summary>Why did my trade fail with "slippage exceeded"?</summary>

The market moved past your tolerance between transaction creation and inclusion. Either raise the tolerance or retry when the market is calmer.

</details>

<details>

<summary>Does slippage apply to limit orders too?</summary>

Yes — your tolerance bounds the price the order is willing to fill at, even on a limit. Limit orders that drift past the tolerance can move to \`Error\`.

</details>

<details>

<summary>Can high slippage put me at risk of MEV?</summary>

Yes. Wide tolerance signals to the network that you'll accept worse fills, which is exactly the gap MEV sandwich bots exploit. Keep it as tight as the pool will allow.

</details>

<details>

<summary>How does slippage interact with Priority Fee?</summary>

Slippage controls \*what price\* you accept; Priority Fee controls \*how soon\* the trade is included. Both matter in volatile markets — raising one without the other rarely helps.

</details>


---

# 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/slippage.md?ask=<question>&goal=<endgoal>
```

`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.