> For the complete documentation index, see [llms.txt](https://docs.trybasket.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trybasket.live/introduction/what-is-basket.md).

# What is Basket

Basket turns a strategy on Base into one investable token.

The creator defines the recipe.

The pool holds the assets.

The investor holds one tokenized claim on that pool.

{% hint style="info" %}
One basket token gives one position in a full strategy.
{% endhint %}

### The short model

A basket is a set of Base tokens with target weights.

When someone invests, Basket routes the deposit, buys the underlying assets, and mints basket tokens against that backing.

Each token represents a pro-rata claim on the pool.

{% columns %}
{% column %}

#### For investors

Buy one token instead of many.

Exit through redemption at any time.
{% endcolumn %}

{% column %}

#### For creators

Publish a strategy under your X identity.

Define the recipe without taking custody.
{% endcolumn %}
{% endcolumns %}

### Why Basket exists

Following a strategy on Base by hand is operationally heavy.

You need to pick assets, size positions, route swaps, watch drift, and unwind later.

Basket compresses that into one product.

### How Basket is different

Basket is not one house index.

It is a platform for many baskets.

It is also not a custodial fund.

The assets sit on-chain in the basket pool.

Creators define strategy.

They do not hold user funds.

### What one basket token means

One basket token is a current claim on a share of the pool.

If you own 1% of supply, you own a claim on 1% of pool holdings.

It is not a promise of future exposure.

<details>

<summary>What 1:1 backing does not mean</summary>

It does not mean one token equals one unit of every constituent.

It means pool holdings divided by token supply defines what one token redeems for.

It also does not remove market, liquidity, or creator risk.

</details>

### Core properties

| Property        | What it means                                    |
| --------------- | ------------------------------------------------ |
| Strategy format | A defined set of Base tokens plus target weights |
| User asset      | The investor holds one basket token              |
| Backing model   | The token is backed by real assets in the pool   |
| Custody model   | Neither Basket nor the creator takes custody     |
| Token standard  | Each basket token is a B20 `Asset` token         |
| Price anchor    | Open redemption links price to redeemable value  |

### Key terms

| Term           | Plain meaning                                       |
| -------------- | --------------------------------------------------- |
| Basket         | A token portfolio with target weights               |
| Basket token   | The token investors hold                            |
| Creator        | The person or team defining the recipe              |
| Pool           | The on-chain component holding the backing          |
| NAV            | The pool value and per-token fair value anchor      |
| Fixed basket   | A basket whose recipe stays locked                  |
| Managed basket | A basket whose creator can change the recipe        |
| B20            | Base's native token standard used for basket tokens |

### Why B20 matters

Each basket token is a B20 `Asset` token.

B20 is a native Base standard with ERC-20 selector parity.

That keeps basket tokens compatible with wallets, DEXs, explorers, and indexers.

{% hint style="warning" %}
B20 is new on mainnet as of June 25, 2026.

Treat that as real infrastructure risk.
{% endhint %}

### Start in the right place

<table data-view="cards"><thead><tr><th>Page</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td>Investing in a basket</td><td><a href="/spaces/TgpdYA0rXaZvSzlqmOLu/pages/rd4l6pGFOj5rl2iXhNhr">/spaces/TgpdYA0rXaZvSzlqmOLu/pages/rd4l6pGFOj5rl2iXhNhr</a></td></tr><tr><td>Creating a basket</td><td><a href="/spaces/TgpdYA0rXaZvSzlqmOLu/pages/X7SlmOAyBahCcb7u9c0b">/spaces/TgpdYA0rXaZvSzlqmOLu/pages/X7SlmOAyBahCcb7u9c0b</a></td></tr><tr><td>Minting, redemption &#x26; pricing</td><td><a href="/spaces/TgpdYA0rXaZvSzlqmOLu/pages/PYkozoNwFQmtFPi3Xj0m">/spaces/TgpdYA0rXaZvSzlqmOLu/pages/PYkozoNwFQmtFPi3Xj0m</a></td></tr><tr><td>Architecture overview</td><td><a href="/spaces/TgpdYA0rXaZvSzlqmOLu/pages/XnNEKBun2HcUrn58DmqQ">/spaces/TgpdYA0rXaZvSzlqmOLu/pages/XnNEKBun2HcUrn58DmqQ</a></td></tr></tbody></table>


---

# 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.trybasket.live/introduction/what-is-basket.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.