> 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/for-investors/investing-in-a-basket.md).

# Investing in a basket

This page covers what you own, what to verify, what you pay, and how to enter or exit.

### What you are buying

You are buying a tokenized claim on a basket's underlying assets.

The basket token represents a pro-rata share of the pool.

That gives you one position for a whole strategy.

### What to check first

Read a basket page in this order:

1. Fixed or managed
2. Constituents and target weights
3. Creator identity
4. Fees and execution costs
5. Token and pool addresses

If any of those are unclear, disclosure is weak.

| Check                    | Why it matters                       |
| ------------------------ | ------------------------------------ |
| Constituents             | Shows what you actually own          |
| Target weights           | Shows how exposure is distributed    |
| Fixed or managed         | Shows whether the recipe can change  |
| Creator identity         | Shows who stands behind the strategy |
| Fees                     | Shows entry, hold, and exit friction |
| Token and pool addresses | Shows whether disclosure is complete |

### Fixed versus managed

{% columns %}
{% column %}

#### Fixed basket

The recipe stays locked.

Your exposure changes because markets move.
{% endcolumn %}

{% column %}

#### Managed basket

The creator can change constituents or weights later.

Your exposure changes because markets move and decisions change.
{% endcolumn %}
{% endcolumns %}

{% hint style="warning" %}
Check fixed versus managed before anything else.

A managed basket can change after you invest.
{% endhint %}

### What determines your position

| Input                    | Why it matters                           |
| ------------------------ | ---------------------------------------- |
| Basket composition       | Determines the assets you are exposed to |
| Basket supply            | Defines your pro-rata share              |
| Pool holdings            | Defines the real backing                 |
| Fees and execution costs | Affect entry and exit efficiency         |

### Costs to expect

The total cost is never one line item.

| Cost layer            | What it covers                               | Status            |
| --------------------- | -------------------------------------------- | ----------------- |
| Network gas           | Transaction execution on Base                | Live network cost |
| Swap and routing cost | Market execution into or out of constituents | Varies by route   |
| Protocol fee          | Basket-level fee, if any                     | `TBD`             |
| Creator fee           | Optional creator fee or management fee       | Exact rules `TBD` |

Gas and routing costs are execution friction.

Protocol and creator fees are product choices.

Basket should show each cost before confirmation.

### Core risks

Basket simplifies access.

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

| Risk                | What it affects              | Why it matters                        |
| ------------------- | ---------------------------- | ------------------------------------- |
| Asset risk          | Basket value                 | Holdings can fall or fail             |
| Liquidity risk      | Entry, exit, and rebalancing | Thin markets can hurt execution       |
| Creator risk        | Strategy quality             | A creator can choose badly            |
| Managed-basket risk | Future exposure              | The recipe can change after you buy   |
| Infrastructure risk | Execution and accounting     | B20 and product systems are still new |

Read [Risks & disclaimers](broken://spaces/TgpdYA0rXaZvSzlqmOLu/pages/H815MmGEciTAvxuputX1) before you commit capital.

### Use the product

{% tabs %}
{% tab title="Invest" %}

#### Investment flow

1. Connect a wallet on Base.
2. Open a basket page.
3. Review the creator, holdings, weights, mode, and fees.
4. Choose the token you want to spend.
5. Review the quote, slippage, and costs.
6. Confirm the transaction.
7. Receive basket tokens in your wallet.

Basket routes deposits through Base WETH, buys constituents at target weights, and mints against the new backing.
{% endtab %}

{% tab title="Redeem" %}

#### Redemption flow

1. Connect the wallet holding the basket token.
2. Choose the basket and redeem amount.
3. Select output mode if the flow supports it.
4. Confirm the burn.
5. Receive pro-rata assets or one routed output token.

There are no protocol lockups in the basket model.
{% endtab %}
{% endtabs %}

### When to walk away

<details>

<summary>Red flags before you transact</summary>

Walk away if managed status is hard to find.

Walk away if fees only appear at the last step.

Walk away if addresses are missing.

Walk away if the thesis sounds clean but the holdings do not match it.

</details>


---

# 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/for-investors/investing-in-a-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.
