> For the complete documentation index, see [llms.txt](https://docs.tanx.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tanx.fi/tech/tech-docupaper/transactional-flow/the-deposit-flow.md).

# The deposit flow

<figure><img src="/files/LoPBO8kUw5LKEKKBhJyq" alt=""><figcaption><p>Deposit flow archtiecture</p></figcaption></figure>

Before User can trade, they need to deposit funds into StarkEx via tanX. To do so, they first deposit funds to the on-chain Starkware contract deployed by tanX. The application should then send a corresponding off-chain deposit transaction, which updates the off-chain state.

### **1.** User deposits funds on-chain. <a href="#alice_deposits_funds_on_chain_spot" id="alice_deposits_funds_on_chain_spot"></a>

Alice executes an on-chain transaction to deposit funds. The deposit operation supports deposits of ETH, ERC-20, ERC-721, and ERC-1155.

The on-chain `deposit` function gets the following parameters:

| `starkKey`        | The public Stark key that corresponds to the vault id.                                    |
| ----------------- | ----------------------------------------------------------------------------------------- |
| `assetType`       | The asset identifier of the token to be deposited.                                        |
| `vaultId`         | The recipient’s off-chain account.                                                        |
| `quantizedAmount` | For ERC-20 and ERC-1155, the amount to be deposited. For ERC-721, this value must be `1`. |

<mark style="color:purple;">**NOTE**</mark> : *A user can deposit to any vault, even to one that they do not own.*


---

# 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.tanx.fi/tech/tech-docupaper/transactional-flow/the-deposit-flow.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.