> 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-predictions/speed-presets.md).

# Speed Presets

**Slow · Fast · Turbo — three knobs that trade execution cost against execution certainty.**

Three speed presets sit on the trading widget and on the Quick Buy strip in Research / Pulse. They are not just labels — each one changes how aggressively the order is submitted, how much slippage tolerance is allowed, and how the order is prioritised at execution.

## The three presets

| Preset             | Use when                                             | Trade-off                                                    |
| ------------------ | ---------------------------------------------------- | ------------------------------------------------------------ |
| **Slow** (default) | Liquid market, no time pressure                      | Lowest execution cost, highest miss risk if the market moves |
| **Fast**           | Active market, you want the fill but not desperately | Middle ground                                                |
| **Turbo**          | Closing-soon market, news event, race to the fill    | Highest cost, lowest miss risk                               |

## What each preset actually changes

* **Slippage tolerance** — how much worse than the displayed price the order is allowed to fill. Slow = tight; Turbo = wide.
* **Order routing aggressiveness** — Slow tries to fill at top of book; Turbo is willing to walk multiple levels.
* **Priority fee / gas / tip** — higher speed = higher tip to the execution layer to land the trade first.

## Choosing by market shape

* **Long-window market, deep book** → Slow. You can wait.
* **Short-window market (24h, 1h)** → Fast. You don't have all day.
* **Closing-soon (<5 minutes)** → Turbo. You need this fill now or it's over.
* **News event just broke** → Turbo. Speed beats price; everyone else is also racing.

## Choosing by intent

* **Building a position over time** → Slow. Multiple small Limits, no urgency.
* **Following a Pulse signal** → Fast usually; Turbo if it's in Closing Soon.
* **Closing a position before resolution** → Turbo. Don't get cute with the exit.

## Setting your default

Trading Settings stores a default Speed preset that every market and every Quick Buy click uses. Change the per-click preset on the widget when you want to override the default without changing it permanently. See [Trading Settings](/graphdex-docs/trading-predictions/trading-settings.md).

{% hint style="warning" %}
Turbo is opt-in. It will spend more to land your trade and it will accept worse fills to do so. Use it deliberately — not as a habit.
{% endhint %}

## FAQs

<details>

<summary>Does Turbo guarantee my order fills?</summary>

No. Turbo improves the odds of a fast fill but cannot create liquidity that doesn't exist. On a thin market, Turbo still walks the book and stops when there are no more counterparties.

</details>

<details>

<summary>If Turbo accepts worse fills, why use it ever?</summary>

Because the alternative — missing the trade on a closing-soon or news-driven market — is sometimes worse than paying a few cents more.

</details>

<details>

<summary>Can I customise the exact slippage tolerance per preset?</summary>

Trading Settings exposes a slippage slider. The preset chooses sensible defaults; you can tighten or loosen them.

</details>

<details>

<summary>Does Speed preset affect Limit orders?</summary>

Limit orders post at the price you specify — Speed mostly applies to Market orders. On Limit, the preset affects only the submit priority (how fast the order itself lands on the book).

</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-predictions/speed-presets.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.