> 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/using-shuffle/withdraw.md).

# Taking your money out

Redeem some or all of your **XSHUFFLE receipt** for ETH or the underlying tokens.

1. Open **Index**, connect your wallet and select **Redeem**.
2. Enter how much XSHUFFLE to redeem.
3. Choose **ETH** or **All memes**.
4. Review the amounts and exit fee, confirm in your wallet and wait for confirmation.

## Receive ETH

The Shuffle Index sells your share of every holding and sends you ETH, minus the exit fee and trading costs. Any WETH in your share is converted to ETH too.

## Receive the tokens

Choose **All memes** to receive your share of every holding without selling anything, including SHUFFLE and any WETH (which stays wrapped). You get the full mix; you can't pick individual coins.

The exit fee is taken in XSHUFFLE before the rest is exchanged for tokens.

An ETH withdrawal depends on the trades succeeding; a token withdrawal avoids trades but still depends on each token transferring. Either way, you can get back less than you deposited.


---

# 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/using-shuffle/withdraw.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.