Swap SOL on Arbitrum to AVAX on Linea

FromArbitrum
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.
AVAX / USD
Price
24h
High
Low
Vol

What you need to know

SOL input identity and handling

Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 9 decimal places. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.

Arbitrum to Linea L2 handoff

This route crosses two L2 execution environments. Arbitrum settles to ethereum, while Linea settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.

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

AVAX output identity and receiving

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.

Arbitrum source execution

Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Arbitrum. EVM 0x account address On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval.

EVM-to-EVM execution boundary

Arbitrum and Linea 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 SOL Arbitrum to AVAX Linea

Route-specific mistakes include sending on a network other than Arbitrum; using a destination that is not valid for Linea; running out of ETH before the source transaction is submitted. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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 SOL → AVAX

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

Related routes

Swap SOL on Arbitrum to AVAX on Linea FAQs

What exactly leaves Arbitrum as SOL?

SOL is a contract representation on Arbitrum with 9 decimals at 0x2bcC6D6CdBbDC0a4071e48bb3B969b06B3330c07. ETH, not SOL, pays gas unless both symbols are the same. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.

What exactly arrives on 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 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.

Why does the SOL to AVAX direction matter?

Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. On receipt, Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

What changes between the source and destination asset roles?

SOL is the deposited native-asset input; AVAX 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 SOL?

Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. 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.

What funds the Arbitrum source transaction?

ETH is the native gas asset for Arbitrum. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. SOL is token-tracked and can need approval before transfer.

What is the most dangerous wrong-network mistake here?

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

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

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