Bridge AVAX from Polygon to Linea

FromPolygon
ToLinea
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

Polygon → Linea

Asset

AVAX

Source gas

POL

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the AVAX asset and Polygon network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Linea 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 Polygon. The recorded Polygon 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.

From Polygon L1 into Linea L2

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

AVAX destination 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. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

Linea receipt-side execution

Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Linea. EVM 0x account address A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract.

Polygon deposit-side execution

Polygon is a L1 EVM network in the Polygon ecosystem. POL pays source-side network gas on Polygon. EVM 0x account address A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1.

Polygon to Linea bridge mistakes

Route-specific mistakes include sending on a network other than Polygon; using a destination that is not valid for Linea; running out of POL before the source transaction is submitted. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token 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

Polygon wallet, token-transfer, contract, log, and gas activity remain public, and Linea wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Polygon to AVAX on Linea 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 Polygon → Linea
  • Shows what remains public on Polygon and Linea before you deposit
Check Private Route availability →

Related routes

Polygon to Linea FAQs

What AVAX representation leaves Polygon?

AVAX is a contract representation on Polygon with 18 decimals at 0x2C89bbc92BD86F8075d1DEcc58C7F4E0107f286b. POL, not AVAX, pays gas unless both symbols are the same. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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 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 receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token 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 AVAX contract token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token 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 Polygon address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Polygon, selecting a representation not listed by the quote, or entering an address invalid for Linea can prevent normal detection or receipt.

Can I bridge AVAX from Polygon to Linea without KYC?

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