> For the complete documentation index, see [llms.txt](https://dasus.gitbook.io/dasus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dasus.gitbook.io/dasus-docs/trading/twap.md).

# TWAP Orders

A **TWAP** (time-weighted average price) order executes a size in sub-orders spread over a period you choose, aiming for an average price close to the market's average over that window instead of one print. On Dasus a TWAP is **Hyperliquid's native TWAP**: once you submit it, the protocol slices and executes it on-chain. You do not need to keep the app open.

TWAP is one of the **Pro ▾** order types in the [Pro terminal](https://dasus.gitbook.io/dasus-docs/the-app/web-terminal.md), on perps and spot.

## Why use a TWAP

A single large market order walks the book: each successive fill is worse than the last. A TWAP spreads that impact over time. Use it when your size is large relative to the market's liquidity, when you want an average price rather than a single print, or when you want hands-off execution.

{% hint style="info" %}
To spread an order across a **price range** rather than across **time**, use a [Scale order](https://dasus.gitbook.io/dasus-docs/trading/scale-orders.md): a TWAP executes at prevailing prices as time passes, a Scale rests limit orders at the levels you choose.
{% endhint %}

## Placing a TWAP

1. Select **TWAP** in the order form and choose **Buy / Long** or **Sell / Short**.
2. Enter the **Total Size** (in the coin or in USDC).
3. Set the **Run Time** in hours and minutes.
4. Optionally set a **Trigger price**: the TWAP does not start until the mark price reaches it (from below if you set it above the current price, from above if below).
5. Optionally set a **Max price** (buying) or **Min price** (selling): if the mark crosses it, the TWAP ends and whatever is left is cancelled — it does not resume. The form refuses a level that would end the TWAP instantly.
6. Tick **Randomize** if you want it: *Randomly adjusts each sub-order size (typically up to ±20%) so the TWAP is harder to detect. All other limits still apply.*
7. Tick **Reduce Only** (perps) if the TWAP is meant to close a position.
8. Review Order Details and confirm.

Order Details shows **Frequency: Dynamic (min. 30s)**, **Run Time**, **Order Count: Up to N** and **Order Value**. The count is an upper bound, because Hyperliquid decides the interval.

## The rules

These come from Hyperliquid's TWAP engine, not from Dasus:

| Rule                          | Value                                                                                                                   |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Minimum size**              | $100 notional per TWAP (the button reads *TWAP minimum is $100* until it passes)                                        |
| **Duration**                  | 5 minutes to **24 hours** on Dasus (Hyperliquid itself allows up to 7 days; the longer durations are not available yet) |
| **Sub-order interval**        | Dynamic — derived from the size and the duration, never more often than every 30 seconds                                |
| **Slippage per sub-order**    | Up to 3%                                                                                                                |
| **Catch-up sub-orders**       | If a slice falls behind, the next can be up to 3× the normal size                                                       |
| **Trigger / Max / Min price** | Optional, as described above                                                                                            |

{% hint style="success" %}
**TWAP orders pay no Dasus platform fee.** Hyperliquid's TWAP action cannot carry a builder code, so each slice is charged the protocol's rate only. See [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md).
{% endhint %}

Each executed slice is a fill and pays the protocol's trading fee like any other order.

## Monitoring a running TWAP

* **In the order form** — while a TWAP is running, an **Active TWAPs** card shows Filled (executed / total), Ends in, Avg price, Current price and Elapsed, with a **Cancel** button.
* **TWAP tab** of the bottom panel — three sub-tabs: **Active** (Market, Size, Executed Size, Average Price, Running Time / Total, Reduce Only, Creation Time, **Terminate**), **History** (every TWAP with its status: Activated, Terminated, Finished or Error, plus Randomize and Duration) and **Fill History** (the individual slices).
* **Trade History** — every slice is a normal fill there too.

The list comes from Hyperliquid's own TWAP history, so a TWAP you started from another front-end on the same account appears here as well, and one that has ended disappears on its own.

You can **terminate** a running TWAP at any time. Slices already executed stay filled — they are part of your position; only the unexecuted remainder is cancelled.

## TWAP vs. other order types

|                    | TWAP                                                               | Market                           | Scale                                         |
| ------------------ | ------------------------------------------------------------------ | -------------------------------- | --------------------------------------------- |
| **Execution**      | Slices over time                                                   | Immediately, full size           | Limit orders across a price range             |
| **Price**          | Average of prevailing prices during the window                     | Best available now               | Only at your levels or better                 |
| **Best for**       | Large size, less impact                                            | Speed and certainty              | Accumulating or distributing at chosen prices |
| **Fill guarantee** | Slices execute as they come due (a Max/Min price can end it early) | Fills inside your slippage bound | May not fill if price never reaches the range |

For everything available in the order form, see [Order Types](https://dasus.gitbook.io/dasus-docs/trading/order-types.md).

## Caveats

* **No price guarantee.** A TWAP executes at whatever prices prevail when each slice runs. In a trending market your average can end up meaningfully better — or worse — than the price when you submitted it.
* **Time exposure.** The market can move while the TWAP works; an adverse move affects both the filled part (an open position) and the remaining slices.
* **Slices are real trades.** In thin markets even slices have some impact.
* **The position is live from the first slice.** Filled size counts toward margin and [liquidation](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md) immediately. You can attach a [TP/SL](https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md) to the resulting position at any time.

{% hint style="danger" %}
A TWAP reduces market impact — it does not remove market risk. Size it relative to your margin, watch the TWAP tab while large orders are working, and protect the resulting position with a stop. See [Margin & Leverage](https://dasus.gitbook.io/dasus-docs/trading-concepts/margining.md) and [Liquidation](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dasus.gitbook.io/dasus-docs/trading/twap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
