Withdraw to Ethereum

Move ETH, KPG, or ERC-20 tokens from Mandala back to Ethereum L1 via the Arbitrum Portal.

Withdrawals go from Mandala back up to Ethereum. They take ~7 days because the optimistic-rollup challenge window enforced by the L1 Bridge has to pass before funds can be released. There is no way to skip this on the canonical bridge.

The 7-day window is non-negotiable

The challenge window is enforced by the L1 contracts. Mandala has no fast path. If you need funds on L1 sooner, use a third-party fast bridge that fronts the funds for a fee. See Faster withdrawals below.

Before you start

A wallet on Mandala Chain (Chain ID 20010) with KPG for gas.
The funds on Mandala that you want to withdraw.
Some ETH on Ethereum L1 to pay for the eventual claim transaction (Step 3 below).

Steps

Initiate on L2

Open the Arbitrum Portal Mandala bridge with the direction reversed:

portal.arbitrum.io/bridge → Mandala to Ethereum

Connect your wallet on Mandala. Pick the token (ETH, KPG, ERC-20) and the amount. Confirm in your wallet. This submits an L2-to-L1 message via the ArbSys precompile at 0x0000000000000000000000000000000000000064.
Wait for the challenge window

The Portal will show your withdrawal as pending with a countdown. The window is approximately 7 days. The exact unlock time depends on when the L2 state root containing your withdrawal is asserted on L1.
Claim on L1

Once the window passes, return to the Portal. Connect your wallet on Ethereum. Find your pending withdrawal in the history tab and click Claim. This triggers an L1 transaction that pulls the funds out of the Outbox at 0x004eF39261cee56409Dbd26040a33Eca8326490C and delivers them to your address on L1.

You pay the L1 gas for the claim. If you do not claim, anyone else can claim on your behalf to your address; the claim is permissionless.

What lands on Ethereum

Token withdrawn	Balance on Ethereum
ETH	ETH balance on Ethereum L1.
KPG	The L1 representation of KPG (the same ERC-20 that the bridge uses on the L1 side).
ERC-20	The original L1 token (or, for tokens with custom bridge logic, the canonical L1 form returned by the gateway).

Why 7 days

The 7-day delay is the optimistic-rollup challenge window. It gives validators time to dispute a bad L2 state root before the L1 Outbox releases funds. Mandala does not set this value; it is the standard Arbitrum dispute period. For the full story, see Trust & Security Model.

Faster withdrawals

Third-party fast bridges sell the wait time for a fee. They monitor your pending L2 withdrawal, front you the equivalent funds on L1 immediately, and collect the canonical withdrawal once the window passes.

The trade-offs:

Pro: funds in minutes instead of days.
Con: you pay a discount fee to the liquidity provider.
Con: trust shifts to the fast-bridge operator until the canonical withdrawal lands.

These services are not part of Mandala's protocol. They are operated by third parties. Examples (not exhaustive, not endorsements): Across, intent-based bridge aggregators.

Tracking the withdrawal

L2 side: explorer.mandalachain.io shows your initiation transaction, including the call to ArbSys.
L1 side: during the wait, no L1 activity. After you claim, the claim transaction shows up on Etherscan against the Outbox contract.

Troubleshooting

The Portal does not show my withdrawal. Confirm the initiation transaction succeeded on the Mandala explorer. Sometimes the Portal takes a few minutes to index a fresh withdrawal.

Claim transaction failing on L1. Most common cause: the challenge window has not actually passed. The Portal countdown is approximate; the L1 contract is the source of truth.

Cannot afford the L1 claim gas. You can wait until L1 gas is cheaper; the withdrawal does not expire. Anyone can claim on your behalf, so a friend with L1 ETH can also do it.