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

# Trading Settings

**Set defaults once — every market inherits them. The settings cog opens the modal.**

The trading defaults modal is reachable from the settings cog on the Research toolbar, on the Pulse lane filter, and on the trading widget itself. Every value here applies across every market unless overridden per click.

## What's in the modal

* **Default amount** — the size loaded into the trading widget when you open a market. Independent from the preset chips, which are a quick-pick overlay.
* **Default speed** — Slow / Fast / Turbo. Applied to Quick Buy clicks and to the widget on every market.
* **Slippage tolerance** — maximum acceptable slippage on Market orders. Slow has a tight default; Turbo loosens it.
* **Confirmation modal** — toggle. Off (default) submits with a single click. On adds a confirmation step before every submit.
* **Show outcomes on Pulse rows** — toggle. When on, Pulse rows for multi-outcome markets expand inline.

## Recommended starting profile

* **Amount**: an amount that matches your normal sizing for this market type. If unsure, leave it at `0.1`.
* **Speed**: `Slow` unless you actively want every click to be aggressive.
* **Slippage**: leave at default for your speed preset.
* **Confirmation**: `On` when you start out — turn it off only when you trust your own clicks.

## Overriding per click

The widget defaults can be overridden per market without changing the modal:

* Tap a different amount preset chip on the widget.
* Switch Speed from Slow → Fast on the widget.
* Type a custom amount.

Per-click changes do **not** modify your saved defaults.

## When to change defaults

* **You switched from testing to real-size trading** — bump the default amount.
* **You moved to a different style of market** (short-window cycles vs long-window events) — adjust default speed to match urgency.
* **You're getting bad fills** — tighten slippage or downgrade Speed.

{% hint style="warning" %}
Default = applies everywhere. A default amount of "1" applied to Quick Buy on the cheapest preset chip means every accidental click is at "1" size. Match defaults to your risk tolerance.
{% endhint %}

## FAQs

<details>

<summary>Are settings synced across devices?</summary>

Most settings are local to your browser. Sign in on a different device and you'll start from defaults until you re-configure.

</details>

<details>

<summary>Does the slippage tolerance apply to Limit orders?</summary>

No — Limit orders fill at the price you specify. Slippage only applies to Market orders.

</details>

<details>

<summary>What happens if I turn confirmation off?</summary>

Every Up/Down/Yes/No/Buy/Sell click submits immediately. No second-step prompt. Faster, riskier.

</details>

<details>

<summary>Can I reset everything to default?</summary>

Yes — there is a Reset button at the bottom of the modal that returns every setting to its first-install value.

</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/trading-settings.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.