> For the complete documentation index, see [llms.txt](https://docs.turbine.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.turbine.exchange/design-decisions/why-unlimited-allowance.md).

# Why Unlimited Allowance

Turbine asks you for unlimited allowance to hide your sell amount.

**TL;DR:** The allowance is unlimited to hide the full sell amount of your order.

When placing an order, you include a signed Permit2 allowance. It allows the TurbineSettler contract to spend an unlimited amount of your sell token for the duration of your order.

When Turbine settles your order on-chain, it uses the allowance you signed to take your sell token from your wallet. All on-chain data is public, so the allowance also becomes public.

Turbine orders are partially fillable, so settlement can happen across multiple blocks. This is common with low-spread orders.

Your allowance becomes public when Turbine settles the **first** part of your order. **If the allowance matched the exact sell amount, the remaining part of your order would become public.**

With unlimited approval, nobody knows whether the settlement they saw on-chain filled the order fully or left an unfilled portion in the orderbook.

Turbine keeps your order private until it is fully settled, which prevents anyone from frontrunning you and gives you better prices.


---

# 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://docs.turbine.exchange/design-decisions/why-unlimited-allowance.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.