> For the complete documentation index, see [llms.txt](https://elysia.gitbook.io/elysia-perps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elysia.gitbook.io/elysia-perps/getting-started/withdraw.md).

# Withdraw

You can request a withdrawal of your collateral back to your wallet at any time. Each request is reviewed within 48 hours. A withdrawal moves funds the opposite way from a deposit: the protocol locks the amount you request, then the smart contract sends the tokens on-chain to your wallet.

> ⚠️ **Withdrawals arrive on Ethereum mainnet.** The token is sent to your wallet address on **Ethereum mainnet (chainId 1)**, the same chain you deposited from. Make sure the receiving wallet supports Ethereum mainnet. See [Network & Contract Addresses](/elysia-perps/reference/network-and-contracts.md).

## How to withdraw

1. **Request a withdrawal.** Enter the amount and confirm. The protocol checks your available balance and immediately **locks** that amount so it can't be spent twice. Your tradable balance drops right away.
2. **The protocol sends it on-chain.** In the background, the contract sends the tokens to your wallet. You don't pay gas for this send. The protocol submits the transaction.
3. **Funds arrive.** Once the on-chain transaction is confirmed, the withdrawal is complete and the locked amount leaves your account.

```
Request ─▶ Balance locked ─▶ On-chain send ─▶ Confirmed ─▶ Tokens in your wallet
```

## Conversion back to your token

You hold and request withdrawals in your collateral's **$1 unit** (EL$ on the live markets). When the tokens are sent on-chain, that $1 unit is converted **back into the underlying token**: the deposit conversion run in reverse, at the **same fixed per-token rate**.

* Because the rate is identical in both directions, a deposit-then-withdraw round trip returns the **same amount of the underlying token** (to 6-decimal precision).
* Example: if EL was credited at roughly 100 EL → 1 EL$ on deposit, then withdrawing 1 EL$ returns roughly 100 EL.

The conversion rate for each supported token is shown in the app, and is explained in [Collateral](/elysia-perps/getting-started/collateral.md).

## Limits and review

* **Minimum withdrawal: 10 EL$** (1,000 EL). Smaller requests are rejected.

Fees and trading losses come out of the same balance, so a deposit of exactly 1,000 EL can fall below this minimum after one trade. Leave room above 1,000 EL if you want to be able to withdraw after a trade.

**Current: every withdrawal is reviewed**

Regardless of size, each request goes through a manual approval step before it is sent on-chain, and **review can take up to 48 hours**. The wait covers the withdrawal review and a cooldown period. Your balance stays locked while the request is pending. If a request is denied, the lock is released and the amount returns to your available balance, so nothing is lost.

{% hint style="info" %}
**Planned: automatic processing for small withdrawals**

Automatic on-chain processing for withdrawals up to **$100** is in development. Once it ships, requests at or below that amount will skip the review step, and only larger withdrawals will be reviewed. This page will be updated when it goes live.
{% endhint %}

## Processing stages

A withdrawal moves through a few states, visible in your withdrawal history:

| State              | What it means                                                           |
| ------------------ | ----------------------------------------------------------------------- |
| **Pending review** | Awaiting manual approval (balance locked). Every withdrawal starts here |
| **Pending**        | Approved; queued for on-chain send                                      |
| **Submitted**      | On-chain transaction sent; waiting for confirmation                     |
| **Confirmed**      | Tokens delivered to your wallet; withdrawal complete                    |
| **Refunded**       | On-chain send failed; balance returned to you automatically             |
| **Denied**         | Review rejected; balance returned to you automatically                  |

## If something goes wrong

Withdrawals are built to **fail safe**:

* If the on-chain send reverts for any reason, your balance is **automatically refunded** to your available balance. You don't need to do anything.
* A locked-but-not-yet-sent amount is never spent twice; the lock is only cleared once the tokens have actually been delivered.

> **Timing.** Every withdrawal is reviewed first, which can take **up to 48 hours**. Once approved, the on-chain send follows and then needs confirmation. Network congestion can extend confirmation time.

## Where to go next

* New deposits: **Getting Started →** [**Deposit**](/elysia-perps/getting-started/deposit.md).
* Understand the $1 unit and conversion rate: **Getting Started →** [**Collateral**](/elysia-perps/getting-started/collateral.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://elysia.gitbook.io/elysia-perps/getting-started/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.
