> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/trader-documentation/how-trading-works-in-symmio/withdrawals.md).

# Withdrawals

When you trade on Symmio, your funds sit inside the protocol rather than in your wallet. You can deposit instantly and trade as much as you like. The only time there's a delay is when you withdraw back out, to your wallet or another EOA.

### The 12-hour cooldown

Symmio uses a **12-hour withdrawal cooldown**. Once you request a withdrawal (after deallocating funds from your trading sub-accounts), those funds are locked for 12 hours before they can leave the system. It's much like the withdrawal delay on an optimistic rollup.

The reason is safety. If something goes wrong, the cooldown gives the protocol's monitoring systems time to react: suspicious activity can be detected, accounts can be suspended, and damage can be contained inside the window.

For a normal trader, this means:

* You can **trade instantly**.
* You can **deposit instantly**.
* When you **withdraw**, there's a **12-hour delay** before the funds reach your wallet.

The old design had a single withdrawal path with a fixed 12-hour wait, plus a separate bridge for instant withdrawals. The latest version folds these into one flexible system with several options.

### Withdrawal options in the latest version

#### Normal withdrawal

The simplest path. You initiate the withdrawal, wait out the cooldown, and finalize. Your funds go straight to your wallet on the same chain, with no provider involved and no fees beyond gas.

#### Express withdrawal

If you need the funds now, an **express provider** can front them to you immediately, then wait out the cooldown and get reimbursed by the protocol afterward. From your side the withdrawal is near-instant. The provider typically charges a small fee.

#### Cross-chain withdrawal

Symmio runs on multiple chains, and you might want your funds on a different chain than the one you're trading on. A **virtual provider** handles this: it accepts the withdrawal on the source chain and delivers your funds on the destination chain, with the collateral reconciliation happening behind the scenes.

#### Express cross-chain withdrawal

Here an express provider fronts your funds immediately on the destination chain, combining instant payout with cross-chain delivery. The express provider and a virtual provider coordinate behind the scenes.

### How it works in practice

If instant withdrawal is available, the frontend builder should offer it; if not, it should show the estimated wait. You can always fall back to the normal 12-hour withdrawal, which is guaranteed to work regardless of provider availability.

When you initiate a withdrawal, you can split it across multiple destinations. For example, you could send 500 USDC to your wallet on Arbitrum and 300 USDC to a different address on Base, all in one request.

### Cancelling a withdrawal

You can cancel a pending withdrawal any time before it's finalized. How that works depends on the type.

For a **standard** withdrawal, cancellation needs no approval and is finalized on-chain.

For **cross-chain (virtual)** withdrawals, once the provider has accepted there's a blackout window near the end of the cooldown where you can no longer cancel on your own. Outside that window you can still cancel immediately; inside it, the cancellation moves to a pending state and needs the provider's approval to go through.

For **express** withdrawals, any cancellation after the provider has accepted needs their approval. There's no free-cancel window, because the provider has already fronted your funds.

{% hint style="info" %}
The legacy bridge withdrawal from the previous version (v0.8.4) still works but is being phased out. The new system replaces it with a more flexible architecture that supports express providers, virtual providers, cross-chain delivery, and multi-destination withdrawals.
{% endhint %}


---

# 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.symm.io/trader-documentation/how-trading-works-in-symmio/withdrawals.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.
