> For the complete documentation index, see [llms.txt](https://docs.epsilon.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epsilon.exchange/products/orders.md).

# Order types

Beyond instant swaps, Epsilon supports **automated on-chain orders** powered by Epsilon smart contracts. You sign an order once; keepers monitor the market and execute it on-chain when its conditions are met. Orders keep working even when the app is closed.

## Limit

Buy or sell when the market reaches a price you set. The order rests until it can be filled at your trigger price or better. Use it to catch dips without watching charts, or to take profit at a target.

## Stop loss

Sell automatically when the price falls to a trigger you set, cutting a loss before it grows. The same mechanic works in the other direction as a **stop buy**: trigger a purchase when price breaks above a level, useful for catching breakouts.

## DCA (Dollar-Cost Averaging)

Split a larger order into recurring buys over time. You configure the total amount, the interval, and the number of executions, and each slice fills automatically at the best available route.

## DCA stop loss

A stop loss that exits **in slices instead of one market sell**. When your trigger is hit, the position unwinds through a series of staged sells. This matters most for low-liquidity memecoins, where dumping a whole position at once craters the very price you exit at.

## Trailing stop

Track the market with a trailing offset. The trigger follows the price up and only fires once the market reverses by your configured percentage, so you ride winners and lock in gains automatically when the trend breaks.

## Trading with ETH

Order contracts settle in ERC-20 tokens, so orders paid with ETH use wrapped ETH (WETH) under the hood. Epsilon handles this for you:

* When you place an order with ETH, the required amount is **wrapped automatically** as an extra step before the order is signed. Your combined ETH + WETH balance is shown as one spendable balance.
* For a **DCA**, the entire budget is wrapped up front. Keep the wrapped balance in your wallet for the duration of the plan so every slice can execute.

## Managing orders

The orders panel shows:

* **Open orders**: active limit, stop, and trailing orders awaiting their trigger.
* **Active DCAs**: recurring orders that have started executing.
* **History**: filled, cancelled, and expired orders, alongside your swaps.

You can cancel open orders at any time; cancellation is an on-chain action confirmed in your wallet.

## How execution works

```
You sign an order  ──►  Epsilon order contract  ──►  Keeper monitors conditions
                                                         │
                                          condition met  ▼
                                                    Order executes on-chain
```

Because orders live on-chain, execution does not depend on Epsilon's interface being open, and no one, including Epsilon, can move your funds outside the exact terms you signed.


---

# 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://docs.epsilon.exchange/products/orders.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.