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

# Making a deposit

**Deposit ETH. Receive XSHUFFLE, your receipt for a share of the basket.**

1. Open **Index**, connect your wallet on Robinhood Chain and select **Deposit**.
2. Enter an amount in ETH or use the dollar display. Payment is always in ETH.
3. Review the XSHUFFLE amount, fee and quote details.
4. Select **Confirm deposit**, approve in your wallet and wait for confirmation.

## What happens to your ETH?

After the entry fee, your ETH buys the basket in its **current proportions**, including any WETH it holds. Depositing does not rebalance the index.

The tokens stay in the Shuffle Index and you receive **XSHUFFLE** for your share. You never need to buy or manage the individual tokens yourself.

XSHUFFLE follows the basket’s value, so you can get back less than you deposited. Any small part of your deposit left unspent by the trades stays in the index as backing for all holders.

If the quote expires or the basket changes before confirmation, request a fresh quote.


---

# 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/deposit.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.