How to Move ETH from Coinbase Wallet to Base?

Understanding the Bridge Mechanism

1. Across operates as a trusted liquidity-based bridge, relying on relayers and bond-backed verification rather than direct smart contract locking.

2. ETH transferred from Ethereum mainnet to Base via Across is not minted or burned; it moves through a pool-based routing system backed by native ETH reserves on both chains.

3. The bridge uses optimistic verification with a configurable dispute window, though Across typically completes transfers in under five minutes without requiring user-initiated challenges.

4. Gas fees are quoted upfront in ETH and include both source-chain transaction cost and relayer fee, displayed before confirmation.

5. Transaction status is trackable via Across’s dashboard using the deposit transaction hash, with real-time updates on relay progress and destination receipt.

Wallet Preparation Steps

1. Ensure MetaMask or Coinbase Wallet is installed on desktop Chrome, Brave, or Firefox — mobile wallets lack full interface support for Across’s current UI.

2. Import or restore your Coinbase Wallet seed phrase into MetaMask if you intend to use MetaMask for bridging, as Across does not natively connect to Coinbase Wallet’s mobile app interface.

3. Verify your wallet holds sufficient ETH on Ethereum mainnet — both for the amount to bridge and for gas, which must be paid in ETH on the source chain.

4. Confirm your wallet’s network is set to Ethereum Mainnet before initiating the bridge; accidental selection of testnets or wrong L1s leads to failed deposits.

5. Double-check that your Base network configuration is added to MetaMask: RPC URL https://mainnet.base.org, Chain ID 8453, Currency Symbol ETH.

Execution Flow on Across Interface

1. Navigate to app.across.to/bridge and click “Connect Wallet” in the top-right corner.

2. Select MetaMask from the wallet options and approve the connection request in your browser extension popup.

3. Set “From” to Ethereum and “To” to Base — Across auto-detects wallet address across chains but requires manual chain selection.

4. Enter the ETH amount, review the estimated time (usually 2–4 minutes), fee breakdown, and destination address preview.

5. Click “Bridge” and confirm the Ethereum mainnet transaction in MetaMask — signature and gas payment occur here.

Post-Transaction Verification

1. After source-chain confirmation, Across displays a “Relaying” status with an estimated completion timestamp.

2. Monitor the transaction using the deposit hash on Etherscan, and cross-reference with BaseScan using the corresponding receipt hash once processed.

3. Switch MetaMask network to Base and refresh your wallet balance — ETH should appear within the stated time window without further action.

4. If ETH does not appear after seven minutes, check Across’s status page for known relayer outages or liquidity shortages on the Base pool.

5. Do not re-submit the same deposit — duplicate hashes may trigger anti-spam filters and delay processing.

Frequently Asked Questions

Q1: Can I bridge ETH directly from Coinbase.com exchange to Base? No. Coinbase.com is a custodial platform. You must first withdraw ETH to a self-custodied wallet like MetaMask or Coinbase Wallet before using Across.

Q2: What happens if I send ETH to Base using the wrong bridge contract address? Funds sent directly to Across’s deposit contract without going through the app interface will not be automatically routed. Manual recovery requires contacting Across support with proof of transaction — success is not guaranteed.

Q3: Why does Across show “Insufficient liquidity” even when Base ETH balance appears high? Liquidity is pool-specific and denominated in USD-equivalent reserves. Across maintains separate ETH/USDC pools per chain pair; low utilization on the Ethereum→Base route triggers this warning regardless of on-chain ETH supply.

Q4: Is it safe to use Across if I see multiple Discord warnings about stuck transactions? Most reported stalls originate from misconfigured wallet networks or expired quotes. Across’s core protocol has no history of fund loss or contract exploit — all bridge logic is open-source and verified on Etherscan and BaseScan.