Bridge Avalanche to Base

FromAvalanche
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

Avalanche → Base

Asset

USDC

Source gas

AVAX

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the USDC asset and Avalanche 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

From Avalanche L1 into Base L2

Avalanche source execution occurs on L1, while Base delivery occurs on a separate L2 ledger that settles to ethereum. AVAX pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.

Avalanche deposit-side execution

Avalanche is a L1 EVM network in the Avalanche ecosystem. AVAX pays source-side network gas on Avalanche. EVM 0x account address An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits.

Select a Base-compatible output

EVM 0x account address ETH is the native gas asset for Base. The quote identifies whether the delivered asset is native, contract-based, or bridged.

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.

Avalanche to Base bridge mistakes

Route-specific mistakes include sending on a network other than Avalanche; using a destination that is not valid for Base; running out of AVAX before the source transaction is submitted. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

Private Route for USDC → USDC

Avalanche 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 Avalanche 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 Avalanche → Base
  • Shows what remains public on Avalanche and Base before you deposit
Check Private Route availability →

Related routes

Avalanche to Base FAQs

Which asset can travel from Avalanche to Base?

The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit Base output before depositing.

Which gas balances matter for this bridge?

An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. 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 Avalanche address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Avalanche, 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 Avalanche to Base without KYC?

Requirements are checked for the live USDC Avalanche 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 →