Bridging to Avalanche means moving an asset onto the C-Chain, the EVM-compatible smart contract chain inside the Avalanche Primary Network. The C-Chain runs at chain ID 43114, settles in one to two seconds, and pays gas in AVAX. It holds multi-billion-dollar DeFi TVL per DeFiLlama as of Q1 2026.
​

The right route depends on the asset. Native USDC flows through Circle's Cross-Chain Transfer Protocol. USDT moves as Stargate-pooled USDT or LayerZero's USDT0. ETH lands via Stargate, Wormhole, or the historic Avalanche Bridge. Each is described step by step below. Bridging to an Avalanche L1 (the post-Etna name for subnets, after Avalanche9000 activated December 16, 2024) is a separate flow, noted briefly at the end.
​

The Avalanche C-Chain runs at chain ID 43114 with AVAX as the gas token. Most EVM wallets (MetaMask, Rabby, Frame, Core) either ship with the network preconfigured or add it via a one-click prompt from chainlist.org. The standard public RPC is api.avax.network, with snowtrace.io as the block explorer.
​

If your wallet does not already show Avalanche, open the Networks panel and add a custom network using the values published in the Ava Labs C-Chain RPC docs:
​

Avalanche's Core wallet ships with the C-Chain, P-Chain, X-Chain, and several Avalanche L1s built in, and is the only wallet that handles the X-Chain to C-Chain handoff natively (relevant if you fund the C-Chain from an exchange that withdraws to X-Chain).
​

You also need a small amount of AVAX for gas before any bridged asset becomes usable. AVAX gas is paid as a burned base fee plus an optional priority tip per the Avax.network gas fees page. Some bridges deposit a small gas drop; if a route does not, fund AVAX from a centralized exchange first.
​

​

Fig 1. Confirm chain ID 43114 before signing any bridge transaction.
​

USDC moves to Avalanche through Circle's Cross-Chain Transfer Protocol. CCTP burns USDC on the source chain, has Circle's off-chain attestation service sign the burn, then mints fresh native USDC on the C-Chain. The result is canonical USDC, not a wrapped IOU. CCTP V2 settles in 30 seconds to a few minutes and is the default native-USDC route in 2026.
​

CCTP V2 launched on Ethereum and Avalanche on March 11, 2025, and has since expanded to 13+ mainnet chains per Circle's developer docs. CCTP V1 (legacy) begins phase-out on July 31, 2026, so newer integrations target V2. Step by step from an EVM source chain (Ethereum, Base, Arbitrum, OP Mainnet, Polygon):
​

Common error: ending up with USDC.e (the legacy bridged token from before native USDC launched on Avalanche) instead of native USDC. USDC.e still trades but has thinner DeFi support. Verify the destination contract matches Circle's native USDC address before signing.
​

USDT has no Circle-style canonical bridge. As of Q1 2026 the two main onchain routes are Stargate's pooled USDT route and LayerZero's USDT0 omnichain token. Both run on LayerZero messaging; the difference is whether you receive native USDT on the C-Chain or USDT0, Tether's omnichain variant. Per LayerZero's ecosystem documentation, USDT0 supports Ethereum, Arbitrum, OP Mainnet, Base, BNB Chain, Avalanche, Polygon, Tron, Solana, TON, Aptos, and Berachain, with multi-billion-dollar deployed supply.
​

Stargate route (receive native USDT on C-Chain):
​

USDT0 route (receive USDT0 OFT on C-Chain):
​

USDT0 and native C-Chain USDT are different contracts. Avalanche DeFi venues may quote one but not the other. If you arrive with the wrong variant, swap on a DEX such as LFJ (formerly Trader Joe) or Pharaoh.
​

ETH on Avalanche is most commonly bridged through Stargate, Wormhole, or the historic Avalanche Bridge. Each produces a slightly different representation of ETH on the C-Chain, and the version your destination protocol expects matters.
​

The Avalanche Bridge, built by Ava Labs and accessible at core.app/bridge, is the original C-Chain bridge for ETH and ERC-20s from Ethereum. It remains operational per status.avax.network. The Avalanche Bitcoin Bridge transitioned to Lombard's infrastructure on January 28, 2026, but the EVM bridge for ETH continues unchanged.
​

Stargate path: open stargate.finance, select ETH and Avalanche, sign. Stargate routes ETH through its pooled liquidity and a LayerZero message; the destination user receives Stargate's representation of ETH on the C-Chain. Settlement runs one to a few minutes.
​

Wormhole path: open portalbridge.com, select ETH and Avalanche, sign. Wormhole locks ETH in the Ethereum core contract, the Guardian network attests, and Wormhole-wrapped ETH mints on the C-Chain. The output is a different contract from Avalanche Bridge ETH and Stargate ETH; confirm which variant your destination pool expects.
​

For long-tail ERC-20s with no canonical Avalanche route, aggregators such as LI.FI, Jumper, and Squid route through whatever combination of bridges and DEX hops produces the best net output. Intent-based routers such as Eco Routes also handle C-Chain destinations across CCTP, Hyperlane, and other rails.
​

Bridging to an Avalanche L1 is a separate flow from C-Chain bridging. The destination is its own chain with its own gas token, validator set, and contract addresses. Most users do not need this, because most stablecoin and DeFi activity still lives on the C-Chain.
​

Per the Avalanche Interchain Token Transfer docs, the canonical L1-to-L1 path uses ICTT on top of Interchain Messaging. Each token has a home contract on the source L1 that locks the asset, and remote contracts on destination L1s that mint a representation. Add the L1 to Core wallet, acquire its gas token, open the L1's ICTT bridge, and sign. The Avalanche Foundation lists 50+ active L1s as of early 2026.
​

Bridge fees stack three components: protocol fee, source-chain gas, and destination gas (usually covered as an AVAX gas drop). Slippage applies on pooled-liquidity bridges (Stargate, aggregator DEX hops) and not on burn-and-mint bridges (CCTP, Wormhole, USDT0).
​

Indicative ranges for transfers landing on Avalanche C-Chain (refresh quarterly):
​

The C-Chain side itself is cheap; AVAX gas runs a fraction of a cent for a simple ERC-20 transfer. The expensive leg is whichever chain you are leaving, especially Ethereum mainnet under load.
​

Most failed or stuck bridges trace to one of four problems: wrong destination chain, no AVAX for gas, the wrong token variant, or a transfer awaiting attestation. Each has a different fix.
​

Wrong destination chain. If you selected an Avalanche L1 instead of the C-Chain, the bridge executes to the wrong destination. Recovery requires bridging back. Verify chain ID 43114 before signing.
​

No AVAX for gas. A fresh wallet that receives bridged USDC or USDT cannot move it. Send a tiny amount of AVAX from an exchange, or use a gasless approval route in a DEX aggregator that pays gas in the bridged token itself.
​

Wrong token variant. The C-Chain has multiple USDC contracts (native CCTP, USDC.e), multiple USDT representations (Avalanche Bridge USDT, Stargate pool USDT, USDT0), and multiple ETH representations. DeFi venues quote pools for specific variants. If a swap shows "no route" or extreme slippage, the variant is likely wrong; swap or re-bridge into the version the destination protocol expects.
​

Awaiting attestation. CCTP, Wormhole, and some LayerZero paths require a second step after the source-chain burn. Check the bridge's transaction status page (cctp.io for CCTP, wormholescan.io for Wormhole) with your source-chain hash. Funds are waiting for the attestation, not lost.
​

CCTP V2 USDC settles in 30 seconds to a few minutes. Stargate and USDT0 transfers settle in one to three minutes. Wormhole and the historic Avalanche Bridge typically take a few minutes after source-chain confirmation. Aggregator routes inherit the underlying bridge's settlement time plus any DEX hop.
​

Most centralized exchanges support direct withdrawals to Avalanche C-Chain for USDC, USDT, AVAX, and major tokens. This is often cheaper than an onchain bridge because the exchange runs its own internal accounting. Select Avalanche C-Chain during withdrawal.
​

No. The C-Chain (chain ID 43114) is one chain inside the Avalanche Primary Network. Avalanche L1s (formerly subnets) are independent chains with their own gas tokens. C-Chain bridges use CCTP, Stargate, Wormhole, or the Avalanche Bridge. L1 bridges use ICTT on top of Interchain Messaging.
​

Sources and methodology. Avalanche C-Chain RPC and chain ID values verified against the Ava Labs C-Chain RPC docs on May 28, 2026. CCTP V2 chain coverage and launch dates from Circle's developer documentation. USDT0 chain coverage from the LayerZero Plasma case study. Avalanche9000 activation from the Avalanche Builder Hub Etna upgrade reference. C-Chain TVL per DeFiLlama as of Q1 2026. Figures refresh quarterly.
​