EVM-to-EVM execution boundary
Ethereum and Avalanche can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Direction
Ethereum → Avalanche
Asset
USDC
Source gas
ETH
Destination gas
AVAX
Choose the USDC asset and Ethereum network you currently hold.
Check the estimated output, fees, timing, and Avalanche destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Ethereum and Avalanche can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Ethereum. EVM 0x account address An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.
EVM 0x account address AVAX is the native gas asset for Avalanche. The quote identifies whether the delivered asset is native, contract-based, or bridged.
Avalanche is a L1 EVM network in the Avalanche ecosystem. AVAX pays destination-side network gas on Avalanche. EVM 0x account address An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract.
Route-specific mistakes include sending on a network other than Ethereum; using a destination that is not valid for Avalanche; running out of ETH before the source transaction is submitted. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract.

Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Avalanche wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Ethereum to USDC on Avalanche 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.
The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit Avalanche output before depositing.
An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. The bridge output does not automatically fund every later gas need.
EVM 0x account address Do not substitute a Ethereum address merely because a wallet displays both networks.
Sending on a network other than Ethereum, selecting a representation not listed by the quote, or entering an address invalid for Avalanche can prevent normal detection or receipt.
Requirements are checked for the live USDC Ethereum to Avalanche 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.