> For the complete documentation index, see [llms.txt](https://docs.shuffle.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shuffle.family/fees/where-fees-go.md).

# Fee flows and buybacks

The Shuffle Index gives SHUFFLE its utility: fee discounts for holders and recurring buybacks funded by index activity.

Half of these fees goes to the team; the rest is allocated as follows:

| Collected fee revenue             | Basket backing | SHUFFLE buyback and burn |
| --------------------------------- | -------------: | -----------------------: |
| SHUFFLE trading fees              |            50% |                        — |
| Shuffle Index entry and exit fees |              — |                      50% |

These percentages divide collected fees, not the whole deposit or trade. The management fee is separate.

## Supporting XSHUFFLE

Half of collected SHUFFLE trading fees is added to the Shuffle Index as WETH. No new XSHUFFLE is created, so existing shares gain backing. The WETH is invested by a later [rebalance](/how-the-basket-works-technical-section/rebalancing.md).

## Supporting SHUFFLE

Half of collected Shuffle Index entry and exit fees funds purchases of SHUFFLE. The purchased tokens are burned, permanently removing them from supply.

Buybacks run daily at **00:30 UTC** when funds and market conditions allow. Anything not spent carries over to the next run. Buybacks are not a price guarantee.

Contract owners can change team recipients and their split on chain. The table shows the configured policy; see [current configured settings](/how-the-basket-works-technical-section/current-settings.md).


---

# 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.shuffle.family/fees/where-fees-go.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.