> 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/creators/design-a-token.md).

# Design a basket

Publish a reusable basket idea, then choose a public pool or deploy one. Each pool follows an immutable basket version.

| Setting                         | What to decide                                                                 |
| ------------------------------- | ------------------------------------------------------------------------------ |
| Basket name and base share name | Pools use these names unchanged on every network.                              |
| Thesis and icon                 | Explain the strategy and its risks clearly.                                    |
| Markets                         | Choose from the available perpetual markets.                                   |
| Direction                       | Long benefits from a price rise; short benefits from a fall, before costs.     |
| Notional weight                 | Each market's share of gross exposure after leverage. Weights total 100%.      |
| Suggested asset leverage        | Each deployment may retain these suggestions or choose other supported values. |

With 100 USDC of available equity, BTC at 60% and 3× plus ETH at 40% and 2× target 150 USDC and 100 USDC of exposure. Basket leverage is 2.5×. See [Token and basket model](/takes-docs/concepts/token-and-basket-model.md#token-and-basket-model).

A small weight can require a larger seed. The app shows the factory pre-fee floor and an estimate that includes mint fees, market lots, and a 1 USDC activation reserve. Launch checks the estimate again. Prices, fees, and fills can still change the result.

All baskets use notional weights. Publication needs no seed. Funding and the exposure review belong to pool deployment.

After deployment, the pool's chain, generated names, composition, asset leverage and initial seed cannot be changed. Publishing basket edits creates a new version for future deployments. Buy and sell percentage fees are fixed at 0.1% (10 bps), plus a signed settlement fee. As the basket's author, you earn 20% of every pool's percentage fees, whoever deployed the pool; see [Fee sharing](/takes-docs/reference/fees-and-limits.md#fee-sharing).

See [Fees and limits](/takes-docs/reference/fees-and-limits.md#fees-and-limits), then [Review and launch](/takes-docs/creators/review-and-launch.md#review-and-launch).


---

# 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/creators/design-a-token.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.