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

# Fees and limits

The percentage fee is 0.1% (10 basis points), plus one settlement fee. The percentage fee is shared with the basket's creator and the app that routed the request; see [Fee sharing](#fee-sharing). These rules describe the [listed beacon deployments](/takes-docs/reference/contract-addresses.md); historical records retain their original fees.

## Fees

```
Settlement fee = max(0.10 USDC, estimated platform gas in USDC × 1.20 + estimated Circle fee)
Total fee = 0.1% of gross amount + settlement fee
```

Review the percentage fee, settlement fee and estimated net before confirming. HTTP quote reviews expire after 120 seconds. The wallet signs a transaction with the reviewed limits; the contract checks those limits against its registry fee and the separate execution deadline. A changed or expired estimate requires a refreshed review. Buy requests and creator seeds invest gross USDC minus both fees. Seed settlement estimates include activation gas. Sales apply the percentage fee to actual gross proceeds and deduct the accepted settlement fee, capped at actual proceeds; selling all your shares can return zero USDC. Trading, funding and HyperCore account costs affect equity naturally and are not charged again as settlement costs.

The minimum request is 10 USDC, except a sale of the full available share balance worth less than 10 USDC. Partial sales require at least 10 USDC of quoted NAV value and positive estimated net proceeds. Seed and execution requirements can require more.

The accepted settlement fee stays fixed through retries. The platform fronts network gas, absorbs later cost increases and retains any surplus. Wallet gas for approvals, requests, cancellation and manual claims is additional. Cancelling an accepted buy request refunds its full USDC without either fee; transaction gas is not refunded. Immediate processing makes that window short, and cancellation can lose the transaction-ordering race.

## Fee sharing

Sharing never changes what you pay: the total stays 0.1% plus the settlement fee. When a request's percentage fee becomes final, the pool sends it to its network's fee distributor, which splits it:

| Share    | Part of the 0.1% fee     | Recipient                                                          |
| -------- | ------------------------ | ------------------------------------------------------------------ |
| Creator  | 20%                      | The basket's author, registered for the pool by Takes              |
| Frontend | 30%                      | The fee address the request named; the platform when it named none |
| Platform | The rest, including dust | The platform fee recipient                                         |

For example, a 1,000 USDC buy pays a 1 USDC percentage fee: 0.20 USDC to the creator, 0.30 USDC to the routing app and 0.50 USDC to the platform. Settlement fees and bridge surplus stay with the platform. A buy refunded after execution keeps its fee, which is split the same way. A sale pays the app that routed the sale, not the one that routed the buy.

Creators and apps claim their earnings for every pool on a network in one transaction to the distributor. A creator share earned before the creator's registration is held for the pool and released at registration.

## Bridge fees

Circle transfer charges are included once in the settlement fee. Ethereum, Base and Arbitrum deposits use Fast CCTP when execution capacity and caps permit, otherwise Standard. Arc and Monad deposits and all return routes use Standard. HyperEVM needs no bridge. Route rates refresh hourly, separately by environment; an unavailable rate prevents a quote. Execution maxFee headroom is an operating safety cap, not an additional user charge. Principal is protected from bridge deductions by the settlement reserve.

Historical records preserve the fees actually charged under their original contracts.

Moving wallet USDC through [Trade](/takes-docs/trade.md#move-usdc-between-networks) is a separate transfer, with its own reviewed Circle fee and wallet gas on both networks. It is not a pool request and does not use a pool settlement fee. [Referral earnings and rebates](/takes-docs/referrals.md) apply only to eligible percentage fees when reward accrual is enabled; the platform pays them from its share.

## Creator eligibility

Publishing a new basket requires 10,000 USDC of lifetime completed gross buy and sell volume unless the wallet has a configured exemption. Pending and cancelled requests do not count. Sign in to check your eligibility. This publication rule is separate from funding an existing public basket’s pool; see [For creators](/takes-docs/creators.md).

## Creation limits

| Item          | Current rule                                                                                                                           |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Basket        | 1–20 distinct eligible markets; positive weights totaling 100%.                                                                        |
| Leverage      | 1× up to the exchange-reported maximum for each leg's market.                                                                          |
| Seed          | At least the factory minimum and enough for every leg's first trade. Defaults are 10 USDC minimum seed and 12 USDC first-leg exposure. |
| Name / symbol | Basket name: up to 32 characters. Base symbol: up to 9 uppercase letters or digits.                                                    |
| Thesis        | Up to 10,000 characters.                                                                                                               |
| Logo          | PNG, JPEG, or WebP, up to 5 MiB.                                                                                                       |

Basket and field limits are app/API rules; direct contracts do not enforce every market check. The app rechecks the current seed requirement and fee cap before launch.

## Trading and timing

Automation uses these defaults. They are configurable service policies, not guarantees of price, exposure or completion time. See [Trading and rebalancing](/takes-docs/concepts/trading-and-rebalancing.md#trading-and-rebalancing) for worked examples and execution sequencing.

| Setting                 | Default behavior                                                                                                                                   |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Leverage drift          | Trigger strictly below 0.8 or above 1.1 times basket target leverage.                                                                              |
| Emergency leverage      | Trigger at or above 1.5 times target; priority over ordinary drift.                                                                                |
| Weight drift            | Trigger when absolute weight deviation exceeds `min(5 percentage points, 20% × target weight)`; wrong-direction exposure also triggers correction. |
| Monitoring              | Check every 5 seconds; a check is not a promise of a trade.                                                                                        |
| After orders            | Wait 10 seconds after successful order responses, or 60 seconds after an unsuccessful response, then refresh positions.                            |
| Quiet checks            | Wait 60 seconds after an idle/unconfirmed check. Emergency can bypass quiet waits, but not post-order waits or a pending capital operation.        |
| Capital-operation wait  | A blocked trading cycle waits 15 seconds before checking again.                                                                                    |
| Minimum adjustment      | 12 USDC notional, with market lot rounding; full closes and redemption small-target closes have exceptions.                                        |
| Order-price tolerance   | 1% with immediate-or-cancel orders.                                                                                                                |
| Builder fee             | 5 bps when approved and applied; one basis point is 0.01%.                                                                                         |
| Core withdrawal reserve | Fixed 0.05 USDC; limits a redemption withdrawal rather than charging another Takes fee.                                                            |

Confirmed accepted requests start processing as soon as funds, confirmations and execution capacity permit. There is no accumulation window or fee-coverage threshold. One executing request, unavailable funds, chains, markets and operator availability can still delay completion.

See [Accounting](/takes-docs/technical-design/accounting-model.md#accounting-model) and [Request status](/takes-docs/reference/status-reference.md#request-status).

Seed minimums use the token's weight model. For notional weights, a leg's pre-fee minimum equity is its trade floor × sum(weight / leverage) / weight, rounded upward. The factory enforces the largest leg requirement and its seed floor. The app also checks a gross estimate with current mint fees, market lot sizes, and a 1 USDC activation reserve. The estimate does not guarantee fills or exact weights after execution.


---

# 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://takes.gitbook.io/takes-docs/reference/fees-and-limits.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.