# Limit Orders

## Limit Orders

Leveraging the elegance of Uniswap v3, Chainlink Automation (Ethereum, Polygon, Optimism, Arbitrum, Binance Smart Chain), and Adrastia (all Oku chains), Oku can enable limit order functionality available for Uniswap v3 pools

Traders can place limit orders within the Limit Orders page after selecting their preferred pool, and confirming that the "Limit" order type is clicked. After entering the input amount and the execution price, the trade can be submitted onchain.

{% hint style="info" %}
By default, Limit Orders are not enabled for every chain, but can be based on demand.
{% endhint %}

Note: Users may experience minimum sizes on Limit Orders. This is a measure put in place to protect networks against sybil attacks.

<figure><img src="https://2779655004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTiDEX3GBnFVAJgYA9mnN%2Fuploads%2FGnhic1L36z3SyQ5aToFF%2FScreenshot%202026-03-13%20at%2011.35.01%E2%80%AFAM.png?alt=media&#x26;token=ffd80cc8-a4a7-4e7c-8e40-30e94fa46dc2" alt=""><figcaption></figcaption></figure>

## How do Limit Orders Work?

Unlike Uniswap v2's requirement to cover the full range, Uniswap v3's concentrated liquidity enables liquidity providers to select specific price ranges. For instance, on Uniswap v2, liquidity providers in the ETH/USDC pool covered the entire price spectrum. In contrast, Uniswap v3 allows providers to choose narrower ranges, such as $1000 to $3000. Oku utilizes this feature to offer limit orders by providing liquidity at a single point within the chosen range. For example, if a user places a bid for 1 WETH at $1500, Oku opens a one-sided liquidity position at $1500 to $1500, effectively a range of zero. Automation helps manage the position, closing it if the price goes below $1500. This empowers users to utilize onchain, trustless limit orders on any Uniswap v3 pool.

### Claiming Limit Orders

If your order is filled, a "Claim" button will become available next to your order. Pressing claim will initiate an onchain transaction to withdraw funds from the Uni v3 position and send the tokens to your wallet. For most chains except Ethereum, there is a small fee of 0.0003 ETH mandated by Uni v3 to claim proceeds from any Limit Order. In regards to all onchain transactions, there is a gas fee associated with claiming your order. Oku does not charge any additional fees on Limit Order trading.

<figure><img src="https://2779655004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTiDEX3GBnFVAJgYA9mnN%2Fuploads%2FMZNQSxA6ZXaTqDoOoHvA%2FScreenshot%202025-08-05%20at%201.09.27%E2%80%AFPM.png?alt=media&#x26;token=5d4be064-bbe4-4240-8d11-23de7153c540" alt=""><figcaption></figcaption></figure>

\
For those interested in the specific flow between wallet, limit contract and Uni v3 liquidity positions, here's a breakdown:

First, the user creates a Limit Order and tokens go from the wallet to the limit order contract. The contract then creates a Uni v3 position in the token pair liquidity pool. When the order gets filled, funds are withdrawn from the Uni v3 position and remain in the contract waiting to be claimed by the user.

## Market Orders

Market Orders on Oku execute near instantaneously as a Users buy or sell order is matched at the current market price for an asset. This is a reliable strategy for traders who aren’t concerned with small price fluctuations.

## Instructional Video

{% embed url="<https://drive.google.com/file/d/1b3CkNk9I8ZL9Yl2qlNuZXk3YjOGrQv0k/view>" %}


---

# Agent Instructions: 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:

```
GET https://docs.oku.trade/home/limit-orders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
