> 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/faq/questions.md).

# Frequently asked questions

## Does buying SHUFFLE mean I own the basket?

No. **SHUFFLE is our utility token**: holding it lowers your entry and exit fees on the official website, and Shuffle Index fees buy back and burn it. SHUFFLE is your bet on the index's success.

To own a share of the basket, deposit into the Shuffle Index and you'll receive XSHUFFLE.

## Do I need SHUFFLE to deposit into the index?

No, but SHUFFLE holdings can reduce your entry and exit fees.

## Do I choose or manage my coins in the index?

No. An automated operator selects and adjusts the basket by fixed rules. Holding XSHUFFLE is your claim on it.

## Is SHUFFLE always exactly 5% of the basket?

No. 5% is the target; holdings drift as prices move, and rebalancing buys or sells SHUFFLE to move back toward it.

## Does the Shuffle Index rebalance hourly?

No. The main rebalance is daily at **12:00 UTC**. Because sales are capped at 0.05% of each token's supply per hour, trimming a large position can continue hourly until done, followed by a fresh assessment for a rebalance that can invest the proceeds. Once the rebalance completes, trading pauses until the next 12:00 UTC. See [rebalancing and accounting](/how-the-basket-works-technical-section/rebalancing.md).

## Why can a rebalance show zero confirmed transactions?

A run can decide there's nothing worth trading, or stop before sending a transaction because of a safety check, missing route, high gas cost or unverified token. A run's timestamp doesn't mean a transaction was sent; check the recorded reason and the transaction receipt.

## Why does a replacement wait while a token is being sold?

A token being sold keeps its slot until it's fully gone, because the index can't hold an extra token even briefly. The final sale and the replacement purchase happen together in one transaction.

## Are fee receipts the same as meme purchases?

No. A fee receipt adds WETH to the index without creating shares. A later rebalance can invest it together with other WETH, so a given purchase can't be traced back to a specific fee receipt.

## What can the owner change?

The owner controls rebalances and can:

* Pause deposits and rebalances, or close deposits permanently.
* Delist a malfunctioning meme. This permanently writes off that token's backing, and holders bear the loss.
* Eject a holder, who receives their share of the underlying tokens. The owner can't redirect those tokens.

Withdrawals stay open while paused or closed, as long as the tokens can transfer (and, for ETH, the swaps can execute). You are trusting the owner with these powers, and trusting the tokens themselves to behave.

## Why did my transaction fail?

A quote may have expired, the basket may have changed, or a trade or transfer may have failed. Read the website’s message and check the transaction status before trying again. If in doubt, feel free to DM [@aleister0x](https://t.me/aleister0x)


---

# 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/faq/questions.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.
