Bridge AVAX from Linea to Avalanche

FromLinea
ToAvalanche
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 → Avalanche

Asset

AVAX

Source gas

ETH

Destination gas

AVAX

How the Sasquatch deposit route works

1. Select the source

Choose the AVAX asset and Linea network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Avalanche 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

AVAX source representation

Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on Linea. The recorded Linea representation uses 18 decimal places. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.

Leaving Linea L2 for Avalanche L1

Linea inclusion and its ethereum settlement are distinct from final receipt on Avalanche. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.

AVAX destination representation

Avalanche is classified as a native asset for this route. AVAX uses a native asset on Avalanche. The recorded Avalanche representation uses 18 decimal places. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

Avalanche receipt-side execution

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.

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.

Linea to Avalanche bridge mistakes

Route-specific mistakes include sending on a network other than Linea; using a destination that is not valid for Avalanche; running out of ETH before the source transaction is submitted. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. 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. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

Private Route for AVAX → AVAX

Linea wallet, token-transfer, contract, log, and gas activity remain public, and Avalanche wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Linea to AVAX 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.

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

Related routes

Linea to Avalanche FAQs

What AVAX representation leaves Linea?

AVAX is a contract representation on Linea with 18 decimals at 0x5471ea8f739dd37E9B81Be9c5c77754D8AA953E4. ETH, not AVAX, 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. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.

What AVAX representation arrives on Avalanche?

AVAX is listed as the native representation on Avalanche; AVAX is used for network gas. 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. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

Does the same AVAX ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a AVAX contract token and a native AVAX. 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. 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.

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 Avalanche can prevent normal detection or receipt.

Can I bridge AVAX from Linea to Avalanche without KYC?

Requirements are checked for the live AVAX Linea 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.

View all bridge FAQs →