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

# Order Types

The Pro order form offers nine order types. All of them are matched on Hyperliquid's on-chain order book: Dasus builds the order, your session key signs it locally, and the fee, margin and estimated liquidation price are shown in Order Details before you confirm (see [Trading Interface](https://dasus.gitbook.io/dasus-docs/trading/interface.md)).

| Order type                   | What it does                                                  | When to use it                                    |
| ---------------------------- | ------------------------------------------------------------- | ------------------------------------------------- |
| **Market**                   | Fills now against the book, within your max slippage          | You want in or out immediately                    |
| **Limit**                    | Rests at your price or better; GTC, IOC or ALO (maker)        | You want price control and can wait               |
| **Stop Market**              | Triggers a market order when the price reaches your trigger   | A stop loss, or a breakout entry, execution first |
| **Stop Limit**               | Triggers a limit order at your price                          | Same, with control over the fill price            |
| **Take Market / Take Limit** | Triggers when the price reaches your profit target            | Locking in gains without watching the chart       |
| **Scale**                    | Splits one order into 2–20 limit orders across a price range  | Building or exiting a position across a zone      |
| **TWAP**                     | Hyperliquid's native TWAP: slices executed over 5 min to 24 h | Large orders with less market impact              |
| **Chase**                    | A post-only limit that follows the best bid/ask until filled  | A maker fill on a market that keeps moving        |

{% hint style="info" %}
**Where each type is available.** Lite: Market and Limit, plus attachable TP/SL. Spot: every type except Reduce Only and attached TP/SL (there is no leveraged position to protect). Prediction markets: Market, Limit and Scale — see [Prediction Markets](https://dasus.gitbook.io/dasus-docs/trading/outcomes.md).
{% endhint %}

## Market

A market order is sent as a limit order that crosses the book, immediate-or-cancel, priced at the mark price plus your **max slippage** (default 8%; change it from the Slippage row in Order Details or in Settings, between 0.1% and 15%). Anything that cannot fill inside that bound is cancelled instead of being filled at a worse price. Order Details shows *Est* — the slippage you would get walking the current book with your size — next to *Max*.

Hyperliquid also caps the notional of a single market order per leverage tier. If your order is above the cap the form warns *This order's notional exceeds the market maximum* — split it or use a limit order.

* **Pros:** immediate, guaranteed to take whatever liquidity is inside your bound.
* **Cons:** pays the taker fee, and on a thin book the average fill can sit well away from the last price.

**Example:** BTC trades around $65,000 and you want long exposure now. You market-buy 0.1 BTC and are filled against the best asks. Your average fill becomes your [entry price](https://dasus.gitbook.io/dasus-docs/trading-concepts/entry-price-pnl.md).

## Limit

A limit order rests on the book and only fills at your price or better: buy limits at your price or lower, sell limits at your price or higher. The price field pre-fills with the current price; **Mid** resets it and clicking a level in the order book copies that price.

**Time-in-force (TIF):**

| TIF                           | Behaviour                                                                                                                                                                                                               |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GTC** (Good-Til-Cancelled)  | Rests until it is filled or you cancel it                                                                                                                                                                               |
| **IOC** (Immediate-Or-Cancel) | Fills what it can immediately; the rest is cancelled                                                                                                                                                                    |
| **ALO (maker)**               | Add-liquidity-only, i.e. post-only: if the order would execute as a taker it is rejected (*The post-only order would cross the book.*) instead of filling. Guarantees the maker rate — and the lower maker platform fee |

{% hint style="info" %}
A GTC limit that crosses the spread fills immediately and pays the **taker** rate. Use ALO when you specifically want maker execution. See [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md).
{% endhint %}

**Example:** ETH trades at $3,450 and you want to buy a dip. You place a GTC limit buy at $3,380; it rests and fills only if the market trades down to your level.

## Stop Market and Stop Limit

A stop stays inactive until Hyperliquid sees the **mark price** reach your **Trigger price**; then it becomes a market order (Stop Market) or a limit order at the limit price you typed (Stop Limit). The form checks the direction before sending: *A buy stop must trigger above the current price* and *A sell stop must trigger below the current price*.

* **Stop Market** is sent, when triggered, as a market order with a price bound at least 5% past the trigger. In a fast market the fill can be some distance from the trigger.
* **Stop Limit** never fills beyond your limit price — but if the market gaps through it, it may not fill at all.
* Trigger orders **do not reserve margin**: if your free margin runs out before the trigger, the order is cancelled. The form prints this note on every trigger order that is not reduce-only.
* Tick **Reduce Only** when the stop is meant to close a position.

{% hint style="warning" %}
For a stop loss you rely on, a Stop Market is normally the safer choice: a Stop Limit protects the fill price, not the execution. Keep a buffer between the stop and your estimated liquidation price — see [Liquidation](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md).
{% endhint %}

When a stop protects the position you already hold (closing side, and either reduce-only or no bigger than the position), placing it replaces the previous stop of the same kind: Dasus keeps **one SL and one TP per position**. A stop meant as an entry is left untouched. See [Take Profit / Stop Loss](https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md).

**Example:** you are long BTC from $65,000 and set a Stop Market sell with trigger $63,500 and Reduce Only on. If the mark reaches $63,500 the position is closed at market.

## Take Market and Take Limit

The mirror of a stop: it triggers when the price reaches your profit target. The direction check is the reverse — *A buy take profit must trigger below the current price*, *A sell take profit must trigger above the current price* — and the same one-TP-per-position rule applies. Take Market fills at market when triggered; Take Limit places a limit order at your price.

To set a take profit and stop loss that follow an open position (and scale with it), use the position's **TP/SL** instead — see [Take Profit / Stop Loss](https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md).

## Scale

A scale order splits one size into **2 to 20** limit orders spaced evenly between a **Start** and an **End** price. **Skew** weights the sizes linearly from the first order to the last (1 = equal sizes; 2 = the last order is twice the first). Each sub-order must be worth at least $10, the ladder is sent as a single batch, and the TIF you pick applies to every sub-order.

**Example:** instead of one limit buy at $3,380 you scale-buy ETH from $3,400 down to $3,300 in 10 orders with a skew above 1, so more size sits at the lower prices.

Full details in [Scale Orders](https://dasus.gitbook.io/dasus-docs/trading/scale-orders.md).

## TWAP

A TWAP hands the order to Hyperliquid, which executes it in sub-orders spread over the duration you set (5 minutes to 24 hours on Dasus) with an interval it decides — never faster than one every 30 seconds. Minimum $100 per TWAP. Optional trigger price and max/min price. Running TWAPs appear in the **TWAP** tab and in the order form, where you can terminate them. TWAPs pay **no Dasus platform fee**.

Full details in [TWAP Orders](https://dasus.gitbook.io/dasus-docs/trading/twap.md).

## Chase

A chase rests a **post-only (ALO) limit at the best price on your side of the book** — the best bid when buying, the best ask when selling — and re-prices it whenever that best price moves, so your order keeps sitting at the front of the book and every fill is a maker fill.

How it runs:

* The loop lives **in your browser tab**. Every 1.5 seconds it checks the order's status and, if the best bid/ask moved, cancels and re-places it at the new price. The **Chase Price** row shows the price it is pegged to, and the form shows **Re-pegs** and **Filled** while it runs.
* **Max chase distance** (optional): once the price is that far from where the chase started, the order stops following and rests there as a normal limit. If the market comes back inside the distance, the chase resumes.
* Partial fills are handled: the remaining size keeps chasing. When the remainder falls below the $10 minimum the chase completes.
* It stops on its own if it hits Hyperliquid's rate limit repeatedly, and [Guardian Mode](https://dasus.gitbook.io/dasus-docs/trading/guardian-mode.md) re-checks each re-peg.
* The order form runs **one chase at a time**, and a chase always asks for confirmation first.

{% hint style="warning" %}
**A terminated chase leaves its order on the book.** Pressing **Cancel Chase**, switching market, closing or refreshing the tab, or disconnecting stops the re-pricing — but the order that was resting at that moment **stays open as a normal limit order** until it fills or you cancel it from Open Orders. The confirmation popup says exactly this before you start.
{% endhint %}

The **Chase** tab of the bottom panel lists active chases (size, executed size, max distance, % filled, Terminate) and a history of filled and terminated ones. The list only lives for the session of that browser tab, because Hyperliquid has no record of a chase — only of its orders.

**Example:** you want to buy ETH as a maker while the price drifts up. Instead of cancelling and re-placing your bid every few seconds, you start a chase: it keeps your bid at the best bid, filling at the maker rate, until it is done or the price runs past your max chase distance.

## Reduce Only

Available on every perps order type, including Scale, TWAP and Chase. A reduce-only order can only decrease or close your position: it never opens or flips one, and Hyperliquid rejects it if it would. With Reduce Only on, the size slider's 100% means your whole position, and the form blocks a size larger than the position (*Amount exceeds position size*). Reduce-only orders are never evaluated by Guardian Mode.

## Attached TP/SL

Market and Limit orders on perps can carry a take profit and/or stop loss. They are sent in the same action as the entry and become active when the entry fills. See [Take Profit / Stop Loss](https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md).

***

{% hint style="success" %}
Whichever type you use, Order Details shows the order value, the margin required, the fee as taker / maker and — on perps — the estimated liquidation price **before** you confirm. Review it every time: see [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.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/order-types.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.
