How to Claim Your Arbitrum Bridge Withdrawal After 7 Days

If you moved ETH or tokens from Arbitrum back to Ethereum mainnet and are now staring at a transaction that seems “stuck,” you are not alone — and nothing is broken. Withdrawals on Arbitrum’s canonical bridge deliberately take about seven days to finalize, and the last step does not happen on its own. You have to come back and claim your funds with a second transaction.

In this guide you will learn why the seven-day window exists, how the two-transaction withdrawal flow works, the exact steps to claim your withdrawal once the window closes, what fees and timing to expect, what can go wrong along the way, and how to spot the phishing sites that target people waiting on withdrawals.

id=”why-seven-days”>Why Arbitrum withdrawals take about 7 days

To understand the claim step, it helps to understand why the wait exists at all. Arbitrum is an optimistic rollup. “Optimistic” here is a technical term: the network assumes the batches of transactions it posts to Ethereum mainnet are valid, and it gives anyone watching a window of time to prove otherwise. That window is the challenge period, and it is set to roughly seven days.

During those seven days, anyone can submit a fraud proof if they detect an invalid state transition. If a challenge succeeds, the bad batch is rejected and the chain is corrected. If nobody challenges — which is the normal case — the withdrawal becomes final and your funds are releasable on mainnet. The delay is not a bug or a fee-collection trick; it is the core security mechanism that lets an optimistic rollup inherit Ethereum’s security without re-executing every transaction on mainnet.

This is also why deposits (Ethereum → Arbitrum) are fast while withdrawals (Arbitrum → Ethereum) are slow. Moving money into the rollup only requires Ethereum to accept the deposit — there is nothing to challenge. Moving money out requires the rollup’s state to be proven final first. Every optimistic rollup works this way; Arbitrum’s window is simply one of the longest, at around seven days.

One common misunderstanding: the seven days do not start when you feel like it. The clock starts when your withdrawal transaction is included on Arbitrum (the L2). From that block onward, you are in the challenge window. There is no way to pay to skip it on the canonical bridge — the window is a protocol rule, not a priority queue.

How the two-transaction withdrawal flow works

A canonical Arbitrum withdrawal is always two transactions, made days apart, on two different networks:

Transaction 1 — initiate the withdrawal (on Arbitrum). You interact with the bridge contract on Arbitrum and tell it you want to move funds back to Ethereum mainnet. This burns or locks your tokens on the L2 side and creates a withdrawal record. This transaction costs Arbitrum gas (paid in ETH on Arbitrum, which is cheap) and it starts the seven-day challenge clock.

The wait — the challenge window (about 7 days). Your withdrawal sits in a pending state while the challenge period runs. Nothing is required from you during this time. Your funds are not “in” your wallet during the wait, but they are also not lost — they are locked in the bridge contract, releasable only by the address that initiated the withdrawal.

Transaction 2 — claim the withdrawal (on Ethereum mainnet). Once the challenge window has fully passed, you submit a claim transaction on Ethereum mainnet. This proves the withdrawal is final and releases your funds to your mainnet address. This step costs Ethereum mainnet gas, and it is the step most people miss — the bridge does not auto-claim for you.

Think of it like registered mail: transaction 1 drops the package at the post office, the seven days are the holding period while anyone can contest the shipment, and transaction 2 is you showing up with your ID to collect it. Nobody collects it for you.

A useful mental model for tracking: most bridge interfaces show your withdrawal as “pending” with a countdown, then flip it to “ready to claim” or “claimable” once the window closes. If your interface shows no claim button yet, the window simply has not finished — check the timestamp of your L2 initiation transaction and count forward seven days.

Step-by-step: claiming your withdrawal

Here is the practical flow, assuming you already initiated the withdrawal on Arbitrum at least seven days ago. The exact buttons differ between interfaces, but the underlying actions are the same everywhere.

Step 1 — Confirm the challenge window has fully passed. Find your original withdrawal transaction on an Arbitrum block explorer and note its timestamp. Add seven days. Only proceed when that time has genuinely passed — attempting to claim early will simply fail (and still cost you a mainnet gas fee for the failed attempt, so do not guess).

Step 2 — Switch your wallet to Ethereum mainnet. The claim transaction happens on mainnet, not on Arbitrum. Open your wallet’s network selector and switch to Ethereum. Double-check you are on the right network before signing anything — signing a mainnet transaction while thinking you are on Arbitrum is a classic, avoidable mistake.

Step 3 — Open the bridge interface and connect the same wallet. Use the same address that initiated the withdrawal. Withdrawals are tied to the initiating address; a different wallet cannot claim your funds. If you initiated from a hardware wallet, connect that same hardware wallet now.

Step 4 — Find your pending withdrawal and select “Claim.” Look for a “withdrawals,” “history,” or “transactions” tab. Your withdrawal should show as ready or claimable. Select it and start the claim flow. The interface will show you what you are about to receive and the estimated mainnet gas cost.

Step 5 — Make sure you have enough ETH on mainnet for gas. The claim is a mainnet transaction, so you need ETH on Ethereum mainnet — not on Arbitrum — to pay for it. If your mainnet balance is empty because everything sits on Arbitrum, you will need to get a small amount of ETH to mainnet first (even a modest amount from an exchange withdrawal works). This is the single most common reason claims fail at this step.

Step 6 — Sign and submit the claim transaction. Review the details carefully: the token, the amount, and the destination address should all match what you withdrew. Confirm in your wallet, then wait for mainnet confirmation. Mainnet blocks are slower than Arbitrum’s, so give it a few minutes.

Step 7 — Verify receipt. Once confirmed, check your mainnet wallet balance or look the transaction up on an Ethereum block explorer. Your funds should now be in your mainnet address. If the interface still shows the withdrawal as unclaimed after confirmation, refresh — interfaces sometimes lag behind the chain.

Fees and timing: what to expect

It is worth separating the two cost centers, because they behave very differently. The initiation transaction on Arbitrum is cheap — Arbitrum gas fees are typically a small fraction of mainnet fees, and initiating a withdrawal is a routine contract interaction. The claim transaction on Ethereum mainnet is the expensive one: it executes on L1, so you pay L1 gas prices at whatever the network conditions are when you claim.

Because the claim is on mainnet, when you claim affects what you pay. Gas prices fluctuate with network congestion. Since there is no deadline on claiming — your withdrawal does not expire — you can afford to wait for a quieter moment with lower gas prices if the fee looks painful. Checking a gas tracker before submitting the claim is a sensible habit, and there is no penalty for claiming on day 10 or day 30 instead of day 7.

Timing-wise, the honest summary is: about seven days of waiting, then one mainnet confirmation (roughly 15 minutes to finality in practice, though interfaces may take longer to update). Anyone promising you a canonical withdrawal faster than the challenge window is either describing a different mechanism (see the comparison table below) or not describing the canonical bridge at all.

One more cost to keep in mind: if you bridged a token rather than plain ETH, the claim releases that token on mainnet. You will then hold the token on mainnet, where any further moves (swaps, transfers) also cost mainnet gas. Factor that into your planning if your goal was to sell or move the funds again quickly.

Withdrawal methods compared

The canonical bridge is not the only way to get funds off Arbitrum. The alternatives trade the seven-day wait for different costs and trust assumptions. This comparison keeps it honest — there is no free lunch, only different trade-offs.

A note on the third-party row: these services give you speed by having liquidity already sitting on mainnet — they pay you out from their own inventory and collect your Arbitrum-side funds themselves, absorbing the seven-day wait on your behalf. That convenience is real, but so is the added trust: you are relying on their contracts and their solvency. For a deeper look at how these routes differ in general, see our guide on bridging between Arbitrum and Base, which walks through the same route categories.

Your withdrawal is bound to the flow you started with: the comparison above is for planning your next move, not for rescuing the current one.

What can go wrong (and how to fix it)

Most “stuck withdrawal” panic falls into a short list of causes. Work through these before assuming something is broken.

The seven days are not actually up. This is the cause more often than not. People count from when they started thinking about the withdrawal, or they confuse the initiation transaction with some other transaction. Pull up the actual L2 initiation transaction, read its timestamp, and add seven full days. If the window is not complete, there is nothing to fix — only waiting to do.

You are on the wrong network. The claim must be submitted on Ethereum mainnet. If your wallet is still on Arbitrum, the bridge interface will not show a claimable withdrawal, or the transaction will fail. Switch networks and look again.

You connected a different wallet. Withdrawals are bound to the initiating address. If you use a different account — even another account in the same wallet app — your withdrawal will not appear. Reconnect with the exact address that started it.

No ETH on mainnet for gas. As covered in the steps above, the claim needs mainnet ETH. An empty mainnet balance produces a failed or unbroadcastable transaction. Get a small amount of ETH onto mainnet first.

The interface is lagging. Bridge front-ends cache state and sometimes show stale “pending” labels after the window has closed. Refresh, reconnect your wallet, or check the withdrawal status directly against the chain data rather than trusting the UI’s cached label.

You used a third-party bridge, not the canonical one. If your original withdrawal went through a liquidity bridge or an exchange, there is no seven-day claim step at all — the funds should have arrived quickly, and a delay means something else is wrong. Do not attempt a canonical “claim” for a withdrawal that was never canonical; instead, check that service’s status page and support channels. If you are unsure which route you used, our guide on checking whether a bridge was hacked includes steps for tracing a transaction’s actual path.

Safety checklist before you claim

The waiting period creates a specific attack surface: scammers know you are expecting funds and may be impatient. Run through this checklist every time.

Type the bridge address yourself. Never reach the bridge interface through a link in an email, a direct message, a search ad, or a “support agent” who contacted you first. Type the official address into your browser manually or use a bookmark you created yourself on a previous safe visit.

Expect the claim to look boring. The legitimate claim flow is a plain transaction in your own wallet: token, amount, destination address, gas fee. Anything asking for your seed phrase, asking you to “verify” by sending funds somewhere, or promising to “speed up” your withdrawal for a fee is a scam — full stop.

Check the destination address character by character. Before signing the claim, confirm the receiving address is yours. Clipboard-hijacking malware that swaps addresses is a real and common attack; a quick visual check of the first and last characters (ideally the whole string) costs five seconds.

Ignore “support” that finds you. No legitimate bridge team will DM you about your pending withdrawal, and no real support process asks for private keys or seed phrases. Treat every unsolicited message about your withdrawal as hostile. Our overview of wallet drainers explains exactly how these lures convert one bad signature into an emptied wallet.

Do a small test if you are nervous. If the interface or the amounts look even slightly off, stop. Close the tab, re-derive the official address independently, and start over. There is no time pressure on a canonical claim — a scammer’s greatest asset is your sense of urgency, and the protocol gives you none.

Frequently asked questions

The Bottom Line

Claiming an Arbitrum bridge withdrawal is a simple two-part rhythm: initiate on Arbitrum, wait out the roughly seven-day challenge window, then claim on Ethereum mainnet with enough ETH for gas. The wait is the security model working as designed, not a malfunction — and the claim step is yours to perform, on your schedule, with no deadline. Verify the window from the real transaction timestamp, type the bridge address yourself, ignore anyone offering to “help” with your withdrawal, and you will collect your funds without drama.

This guide is for education only — not financial advice.