Mode Bridge

Mode Bridge is the canonical bridge between Ethereum Mainnet and Mode Mainnet, with third-party routes shown alongside it in the Mode app. It is a fork of the Optimism Standard Bridge: the canonical path escrows your asset on L1 and releases the corresponding balance on L2 through OP Stack cross-domain messaging. Mode's docs list ETH, USDC, USDT and WBTC as canonical assets, and canonically bridged ETH arrives as native ETH on Mode (which is also the gas token), not a wrapped version. The app also surfaces routes powered by LI.FI and other liquidity bridges; those can be faster or reach more chains, but you take on that protocol's contracts and liquidity assumptions on top of Mode's. A route using an automated market maker prices execution from pooled liquidity, so the route type matters when you compare the quote. If you're parking size, the canonical route has the fewest moving parts.

Bridging is a one-signature flow for native ETH and a two-transaction flow for ERC-20 tokens: connect an EVM wallet, pick source chain, destination, asset, amount, and route, then approve the token and sign the bridge transaction. The ERC-20 token standard defines the approval mechanism; native ETH skips it entirely, while a token needs an allowance granted to the route's contract first. On a canonical deposit, funds are locked in the L1 Standard Bridge and minted or released on Mode once the L2 picks up the message. A canonical withdrawal runs the other way: initiate on Mode, prove on Ethereum, sit through the challenge window, then finalize with a second Ethereum transaction. Your wallet controls every signature — the bridge never takes custody in the exchange sense, but escrowed L1 funds do sit in upgradeable contracts while their L2 counterparts exist.

Depositing from Ethereum to Mode generally lands within minutes, and the receiving address is the same EVM address as your L1 wallet. Add Mode Mainnet (chain ID 34443) to your wallet — testnet users want Mode Sepolia (919). ETH is the gas token on Mode: a first-time canonical ETH deposit covers you, but bridging only USDC leaves funds you cannot move until ETH reaches that Mode address. Keep a little ETH on Ethereum too — you'll need it if you ever withdraw back.

Canonical withdrawals from Mode to Ethereum take about seven days because of the optimistic-rollup challenge period. The flow is: initiate the withdrawal on Mode, submit a proof transaction on Ethereum once the state is published, wait out the challenge window, then send the finalization transaction on Ethereum to actually receive funds. Each Ethereum step costs L1 gas, so a small withdrawal can be uneconomic in fees even though the bridge itself charges nothing extra. If you need funds on L1 sooner, a liquidity bridge route can exit faster in exchange for its own fees and trust assumptions. A canonical withdrawal that appears pending during the challenge window has not reached finalization; do not re-initiate the same withdrawal.

Bridge cost is source-chain gas plus whatever route costs the quote shows — the canonical bridge doesn't tack on a separate toll. An Ethereum gas model makes the L1 charge vary with network demand: an Ethereum deposit costs L1 gas at whatever the network is charging that day, while actions starting on Mode cost pennies-level L2 gas priced in ETH. Third-party routes add their own provider or liquidity fees, which the quote screen should itemize. If the route uses an automated market maker, slippage in finance is the difference between the quoted and executed price, not a separate bridge toll. Timing splits cleanly by direction: deposits to Mode are minutes, canonical withdrawals back carry the seven-day challenge period. If a quote looks surprisingly expensive, it's almost always L1 gas on the Ethereum leg — check gas prices and consider waiting for a quieter block rather than abandoning the route.

Mode Bridge is non-custodial in the exchange sense, but its risk profile includes smart-contract, upgrade, permissioning, and phishing risk. The canonical bridge contracts are upgradeable, Mode currently relies on permissioned proposers and challengers, and any ERC-20 approval you grant is a standing allowance against a contract; L2BEAT's Mode profile tracks the current permissioning and upgrade setup. Before signing, verify the URL, the contract address your wallet shows, and the allowance scope; treat unlimited approvals as something you revoke after large moves, not leave standing.

Bridge problems usually fall into four operational states: wrong network, no destination gas, an incomplete withdrawal stage, or a confirmed transaction still waiting on messaging. Wrong network: your wallet is on Ethereum but you're trying to act on Mode (or vice versa) — switch networks, don't re-send. No gas on the destination: funds arrived on Mode but you have no ETH there to move them; bridge a small amount of ETH over to unstick yourself. Stuck-looking withdrawal: check whether it's waiting on the proof step, the challenge window, or finalization — each stage needs its own transaction, and "pending" for days during the challenge period is expected behavior. Confirmed source transaction: the funds are in the bridge mechanism; what you're waiting on is messaging or finalization, not rescue. Mode-side transactions are visible on the Mode explorer.