How to Swap USDC for ETH on Base Using MetaMask?

Connecting MetaMask to Base Network

1. Open MetaMask extension and click the network selector located at the top of the interface.

2. Select “Add network” and choose “Base” from the list of popular networks or manually input the Base Mainnet parameters: RPC URL https://mainnet.base.org, Chain ID 8453, Currency Symbol ETH, Block Explorer URL https://basescan.org.

3. Confirm the addition. MetaMask will automatically switch to Base once saved, enabling interaction with Base-native tokens like USDC.e and native ETH.

4. Ensure your wallet holds sufficient ETH for gas fees on Base—transactions require ETH even when swapping stablecoins.

Importing USDC.e Token into MetaMask

1. On Base, the primary USDC version is bridged USDC.e (Ethereum-bridged), not the native USDCb. Its contract address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.

2. In MetaMask, click “Import tokens”, then select “Custom token” and paste the USDC.e contract address.

3. MetaMask will auto-populate token symbol and decimals; verify they match USDC.e (6 decimals) before confirming.

4. After import, check your asset list—USDC.e must appear with a non-zero balance, indicating successful bridging from Ethereum or receipt via Base faucet.

Initiating the Swap via Built-in MetaMask Swaps Interface

1. Click the “Swap” tab inside MetaMask, ensuring the network is set to Base.

2. Set the “From” field to USDC.e and enter the amount you wish to exchange.

3. Set the “To” field to ETH. MetaMask will display the current price impact, slippage tolerance, and estimated output based on integrated liquidity sources including Base’s native pools and cross-chain aggregators.

4. Adjust slippage tolerance if needed—Base’s volatility profile often warrants 0.5%–1.0% for stable-to-native swaps.

5. Review the transaction summary: gas fee in ETH, expected ETH received, and warning indicators for high price impact or low liquidity.

Confirming and Monitoring the Transaction

1. Click “Swap” to trigger the signature request. MetaMask displays the full transaction details including recipient contract (aggregator proxy), value, and data payload.

2. Approve the transaction after verifying all fields. A second signature may appear if USDC.e approval is not previously granted—this authorizes the swap router to spend your USDC.e.

3. Once confirmed, the transaction hash appears. You can copy it and paste into https://basescan.org to track confirmation status in real time.

4. Finality on Base typically occurs within 1–3 blocks (~2–6 seconds). ETH appears in your wallet balance immediately upon block inclusion.

Frequently Asked Questions

Q1. Why does MetaMask show “USDC” instead of “USDC.e” after import?MetaMask relies on token lists; if Base’s official list isn’t loaded, it may resolve to generic “USDC”. Always verify the contract address matches 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.

Q2. Can I swap using ETH from Ethereum L1 directly on Base?No. ETH used on Base must be native Base ETH. Bridging ETH from Ethereum L1 to Base is required first via the official bridge or a supported Layer 2 aggregator.

Q3. What happens if the swap fails with “insufficient output amount”?This signals slippage exceeded. Increase slippage tolerance or reduce swap size. Do not disable slippage protection entirely—it guards against front-running and oracle manipulation.

Q4. Is the MetaMask Swaps interface non-custodial on Base?Yes. All swap logic executes on-chain via permissionless smart contracts. MetaMask never holds or routes funds—it only signs transactions initiated by the user.