An Avalanche bridge is any onchain route that moves value between Avalanche C-Chain and another network. The C-Chain is Avalanche's EVM-compatible execution environment, and it sits behind almost every consumer-facing token transfer to Avalanche. C-Chain holds roughly $1.7B in stablecoin market cap as of Q2 2026 per DeFiLlama, with USDC the largest share, and that pool of liquidity is what most bridge routes target.
​

This listicle compares the canonical C-Chain routes by mechanism, fees, and speed. Subnet bridging (now L1 bridging after the Avalanche9000 upgrade) is a separate flow, covered briefly near the end. The point is to make routing reality legible so an operator can pick by mechanism, not by marketing.
​

An Avalanche bridge is a protocol that transfers tokens between Avalanche C-Chain and another blockchain. Most routes today fall into four mechanism categories: burn-and-mint (Circle CCTP for native USDC), liquidity-pool unified routers (Stargate on LayerZero), generic messaging with lock-and-mint (Wormhole, Hyperlane warp routes), and aggregator routers that quote across all of them (LI.FI, Squid, Across).
​

The C-Chain is the network users mean when they say "Avalanche" in a wallet context. The X-Chain (asset chain) and P-Chain (platform chain) exist for AVAX transfers and validator coordination, not consumer token routing. Native USDC, USDT, AVAX, and most ERC-20 representations live on C-Chain. The C-Chain docs spell out the EVM compatibility that lets bridges use standard ERC-20 patterns here.
​

Routes differ on three dimensions: whether the destination asset is canonical (Circle-issued native USDC) or wrapped, how fees decompose (protocol fee plus gas plus slippage), and how long settlement actually takes. The table below maps the canonical options against those dimensions.
​

Bridging to Avalanche is different because the network has a multi-chain architecture by design. C-Chain is the EVM smart contract chain users transact on. Avalanche L1s (formerly called subnets, renamed after the Avalanche9000 upgrade activated December 16, 2024) are sovereign chains with their own validator sets. Bridging to an L1 is a separate flow from bridging to C-Chain.
​

Avalanche9000 implemented ACP-77 and replaced the prior 2,000 AVAX continuous-stake requirement for subnet validators with a flat fee starting at 1.33 AVAX per validator per month, per ACP-77. The bridging effect: more L1 destinations exist, but each maintains its own bridge rather than sharing one. C-Chain remains the destination most users actually want.
​

Avalanche was also an early home for canonical bridges. Wormhole supported it near launch alongside Solana and Ethereum, and the original Avalanche Bridge (an Ava Labs operated bridge) handled the early Ethereum corridor. The EVM bridge in Core Wallet remains operational; the original Avalanche Bitcoin Bridge transitioned to Lombard's infrastructure in January 2026. Third-party rails handle most non-BTC volume today.
​

Eight routes cover the practical Avalanche C-Chain landscape in 2026. Each routes a different mechanism, and the right pick depends on the asset, source chain, and how fast settlement needs to be. The table below maps each by mechanism, asset coverage, speed range, and what its fee structure looks like.
​

The aggregators (Squid, LI.FI, Jumper, plus Eco Routes as an intent-based router covered below) sit one layer above CCTP, Stargate, Wormhole, and the rest. They quote across the rails and pick by price plus speed. The named rails do the actual settling.
​

CCTP moves native USDC by burning supply on the source chain, having Circle's off-chain attestation service Iris sign the burn message, and minting fresh native USDC on the destination chain. There is no wrapped representation, no liquidity pool, and no third-party bridge custodian. Circle deployed native USDC on Avalanche C-Chain in 2022 and added CCTP support the following year.
​

CCTP V2 launched on Ethereum and Avalanche on March 11, 2025, per the Circle V2 announcement. V2 added three things to the V1 burn-and-mint primitive: Fast Transfer (8 to 20 second finality via Circle's attestation guarantee), programmable hooks (a destination contract can run atomic logic when USDC arrives), and a versioned message format. As of Q1 2026, CCTP is live on 13+ mainnet chains including Avalanche, and the docs at eco.com/support/en/articles/11813797 walk through the burn-attest-mint cycle in more detail.
​

For an operator routing USDC into Avalanche from Ethereum, Arbitrum, Optimism, Base, Polygon, or any other CCTP chain, this is the canonical path. The destination wallet receives the same USDC contract Circle issues directly. Most aggregators route USDC moves through CCTP when both sides support it, because the alternatives wrap.
​

Wormhole and LayerZero both supported Avalanche near its early growth phase and remain operational in 2026 with broad chain coverage. They share a category (generic cross-chain messaging) but differ on architecture: Wormhole uses a 19-validator guardian set that attests source-chain events; LayerZero uses configurable oracle and relayer pairs per message route.
​

Wormhole was Avalanche's launch-era bridge partner. Per the project's own history, Wormhole's first major Avalanche corridor opened in 2021, alongside its initial Solana-Ethereum link. Today Wormhole supports Avalanche alongside Solana, Ethereum, BNB Chain, Polygon, Aptos, Sui, and 30+ other networks per the Wormhole docs. The Apollo Diversified Credit Securitize Fund (ACRED) selected Wormhole to take the fund onchain across Aptos, Avalanche, and Solana in 2025. Historical role aside, Wormhole today is one rail among several rather than the default.
​

LayerZero handles Avalanche through Stargate (its flagship liquidity-pool unified router) and through OFT-standard tokens like USDT0. USDT0 supports Ethereum, Arbitrum, Optimism, Base, BNB Chain, Avalanche, Polygon, Tron, Solana, TON, Aptos, and Berachain as of Q1 2026. Stargate routes typically settle in 15 to 60 seconds with a 0.06% base fee plus gas; the Solana to Arbitrum corridor often finishes in under 30 seconds per real-world tests in early 2026, and Avalanche routes sit in a similar range.
​

Aggregator routes for Avalanche include LI.FI, Jumper (LI.FI's consumer UI), Squid, Across, deBridge, and Rango. Each composes routes from the rails described above (CCTP, Stargate, Wormhole, Hyperlane) and quotes the user a single output amount with a route chosen by price plus speed.
​

LI.FI and Jumper share a backend and aggregate across CCTP, Stargate, Hop, Connext, Across, and others, with no markup over the chosen sub-route. Squid runs on Axelar messaging plus integrated DEX swaps, so a user can send USDC on Ethereum and receive AVAX on Avalanche in one transaction. Across is an intent-based protocol that uses an optimistic relayer model and its own liquidity for fast EVM-to-EVM settlement.
​

Eco Routes is an intent-based router that aggregates the same rails (CCTP, Hyperlane, LayerZero, and others) and settles USDC across 15 chains including Avalanche, per the Eco Routes overview. Operators routing programmatically (settlement flows, treasury moves, payments) tend to integrate at the router layer rather than picking a specific rail for each transfer.
​

Subnet bridging now means L1 bridging in Avalanche terminology, after the Avalanche9000 upgrade renamed subnets to Avalanche L1s. Each L1 maintains its own bridge to C-Chain rather than sharing a single network-wide bridge. The L1 bridge is generally a separate contract deployed by the L1 team, sometimes built on Hyperlane warp routes, sometimes on Avalanche's own ICTT (Interchain Token Transfer) primitive.
​

Active L1s like Beam (gaming) and Dexalot (orderbook DEX) completed migration in the first quarter following Avalanche9000's December 16, 2024 activation. Progmat, Japan's largest security token platform, is migrating to a dedicated L1 covering tokenized assets worth over ¥439.6 billion (~$2.8 billion), expected by June 2026, per the Datachain announcement.
​

For consumer users, the practical implication is: when a wallet shows "Avalanche" it means C-Chain. Bridging to an L1 requires using that L1's specific bridge UI, often built into the L1's own dApp interface. For L1 bridging step-by-step, see the companion article how to bridge to Avalanche.
​

The right Avalanche bridge depends on three variables: the asset (native USDC versus wrapped USDC versus USDT versus AVAX versus other), the source chain (EVM versus Solana versus Tron), and how patient the user is. The table above ranks by mechanism; the rough rules below cover the common cases.
​

None of these is universally "best." The right pick depends on which mechanism matches the asset and corridor. For a fee-focused view, see the companion cheapest crypto bridge 2026.
​

Sources and methodology. Stablecoin supplies and TVL pulled from DeFiLlama in Q2 2026. Bridge protocol details verified against issuer docs (Circle CCTP V2 announcement March 11, 2025; LayerZero and Stargate docs; Wormhole docs; Avalanche9000 / ACP-77 specification). Speed and fee ranges are typical operating windows, not guarantees.
​