> For the complete documentation index, see [llms.txt](https://docs.gravity.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gravity.xyz/legacy-alpha-mainnet-l2/bridge-back-to-ethereum.md).

# Bridge Assets back to Ethereum (Gravity Alpha, L2)

{% hint style="danger" %}
**Action required — bridge out before November 1, 2026.** Please move **all** of your assets off Gravity Alpha Mainnet (L2) back to Ethereum before **November 1, 2026** — G via the official Gravity bridge, and USDT / USDC / ETH and other assets via Stargate (steps below).
{% endhint %}

{% hint style="info" %}
This page covers **withdrawing** assets from the legacy **Gravity Alpha Mainnet (L2, chainId `1625`)** to Ethereum mainnet. To bring assets in, see [How to Get G (on Gravity Alpha Mainnet, L2)](/legacy-alpha-mainnet-l2/bridge-to-gravity.md).
{% endhint %}

## Bridge G back to Ethereum — official Gravity bridge

Use the official [Gravity Bridge](https://bridge.gravity.xyz/) (native canonical route) to move **G** from Gravity Alpha Mainnet back to Ethereum mainnet.

1. Open <https://bridge.gravity.xyz/> and connect your wallet.
2. Set the **source** network to **Gravity Alpha Mainnet** and the **destination** to **Ethereum**.
3. Select **G**, enter the amount, and submit the withdrawal transaction — the native canonical route is used automatically for G.

The native canonical bridge also handles **DAI** and **WBTC** the same way.

{% hint style="warning" %}
**7-day withdrawal delay.** Like all optimistic rollups, native withdrawals from Gravity Alpha Mainnet to Ethereum have a \~7-day challenge period before the funds can be claimed on Ethereum. If you need G on Ethereum sooner, a liquidity-pool route such as [Symbiosis](https://app.symbiosis.finance/swap) can bridge G in minutes instead of the 7-day wait.
{% endhint %}

## Bridge other assets (USDT, USDC, ETH, …) back to Ethereum — Stargate

For **USDT, USDC, ETH/WETH**, and any other asset Stargate supports, use [Stargate](https://stargate.finance/bridge) to bridge from Gravity Alpha Mainnet back to Ethereum mainnet. Stargate uses liquidity pools (Stargate V2 Hydra), so transfers settle in minutes — there is no 7-day rollup wait.

1. Open <https://stargate.finance/bridge> and connect your wallet.
2. Set **From** to **Gravity** (Alpha Mainnet) and **To** to **Ethereum**.
3. Select the asset (USDT, USDC, ETH, …) and amount, then confirm.

| Asset      | Contract on Gravity Alpha Mainnet          | Contract on Ethereum                       |
| ---------- | ------------------------------------------ | ------------------------------------------ |
| ETH / WETH | 0xf6f832466Cd6C21967E0D954109403f36Bc8ceaA | Native ETH                                 |
| USDT       | 0x816E810f9F787d669FB71932DeabF6c83781Cd48 | 0xdAC17F958D2ee523a2206206994597C13D831ec7 |
| USDC       | 0xFbDa5F676cB37624f28265A144A48B0d6e87d3b6 | 0xA0b86991c6218b36c1D19D4a2e9Eb0cE3606eB48 |

{% hint style="info" %}
Keep a small amount of **G** on Gravity Alpha Mainnet to cover gas for the bridge transaction.
{% endhint %}

## See also

* [How to Get G (on Gravity Alpha Mainnet, L2)](/legacy-alpha-mainnet-l2/bridge-to-gravity.md) — bringing assets **in**.
* [Gravity Bridge](https://bridge.gravity.xyz/) · [Stargate](https://stargate.finance/bridge) · [Symbiosis](https://app.symbiosis.finance/swap)


---

# 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.gravity.xyz/legacy-alpha-mainnet-l2/bridge-back-to-ethereum.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.