Swap AVAX on Linea to SOL on Ethereum

FromLinea
ToEthereum
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.
SOL / USD
Price
24h
High
Low
Vol

What you need to know

AVAX input identity and handling

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 Ethereum L1

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

Ethereum destination execution

Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Ethereum. EVM 0x account address An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.

SOL output identity and receiving

Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Ethereum. The recorded Ethereum representation uses 9 decimal places. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Linea source 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.

EVM-to-EVM execution boundary

Linea and Ethereum can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.

Mistakes specific to AVAX Linea to SOL Ethereum

Route-specific mistakes include sending on a network other than Linea; using a destination that is not valid for Ethereum; 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 Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Private Route for AVAX → SOL

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

Related routes

Swap AVAX on Linea to SOL on Ethereum FAQs

What exactly leaves Linea as AVAX?

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 exactly arrives on Ethereum as SOL?

SOL is a contract representation on Ethereum with 9 decimals at 0xD31a59c85aE9D8edEFeC411D448f90841571b89c. ETH, not SOL, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Why does the AVAX to SOL direction matter?

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. On receipt, Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

What changes between the source and destination asset roles?

AVAX is the deposited native-asset input; SOL is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending AVAX?

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 source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

What funds the Linea source transaction?

ETH is the native gas asset for Linea. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. AVAX is token-tracked and can need approval before transfer.

What is the most dangerous wrong-network mistake here?

Sending AVAX on a network other than Linea, or using an address that is not valid for Ethereum, can prevent detection or delivery. Match both network labels and representations to the active route.

Can I swap AVAX on Linea to SOL on Ethereum without KYC?

Requirements are checked for the live AVAX Linea to SOL Ethereum 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 Help Center FAQs →