Bridge USDC from Linea to Base

FromLinea
ToBase
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

Direction

Linea → Base

Asset

USDC

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the USDC asset and Linea network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Base destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

USDC representation on both sides

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. The same stablecoin ticker does not make the two network records or contracts interchangeable.

ETH source gas and ETH destination readiness

A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

Linea to Base L2 handoff

This route crosses two L2 execution environments. Linea settles to ethereum, while Base settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.

Linea deposit-side execution

Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Linea. EVM 0x account address A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones.

Base receipt-side execution

Base is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Base. EVM 0x account address A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

Linea to Base bridge mistakes

Route-specific mistakes include sending on a network other than Linea; using a destination that is not valid for Base; running out of ETH before the source transaction is submitted; selecting a stablecoin by ticker without checking its network contract. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Private Route for USDC → USDC

Linea wallet, token-transfer, contract, log, and gas activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Linea to USDC on Base path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.

  • Reduces the obvious link between the USDC deposit and USDC receipt
  • Compare standard and Private Route options for Linea → Base
  • Shows what remains public on Linea and Base before you deposit
Check Private Route availability →

Related routes

Linea to Base FAQs

What USDC representation leaves Linea?

USDC is a contract representation on Linea with 6 decimals at 0x176211869cA2b568f2A7D4EE941E073a821EE1ff. ETH, not USDC, pays gas unless both symbols are the same. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.

What USDC representation arrives on Base?

USDC is a contract representation on Base at 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913. ETH, not USDC, pays gas unless both symbols are the same. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Does the same USDC ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a USDC contract token and a USDC contract token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. The bridge output does not automatically fund every later gas need.

What destination address should be used?

EVM 0x account address Do not substitute a Linea address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Linea, selecting a representation not listed by the quote, or entering an address invalid for Base can prevent normal detection or receipt.

Can I bridge USDC from Linea to Base without KYC?

Requirements are checked for the live USDC Linea to Base quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.

View all bridge FAQs →