Swap ETH on Scroll to AVAX on Avalanche

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

What you need to know

ETH input identity and handling

Ethereum is classified as a native asset for this route. ETH uses a native asset on Scroll. The recorded Scroll representation uses 18 decimal places. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.

Leaving Scroll L2 for Avalanche L1

Scroll 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.

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

AVAX output identity and receiving

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.

Scroll source execution

Scroll is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Scroll. EVM 0x account address A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently.

EVM-to-EVM execution boundary

Scroll and Avalanche 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 ETH Scroll to AVAX Avalanche

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Avalanche; running out of ETH before the source transaction is submitted. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. 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 ETH → AVAX

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

Related routes

Swap ETH on Scroll to AVAX on Avalanche FAQs

What exactly leaves Scroll as ETH?

ETH is listed as the native representation on Scroll; ETH is used for network gas. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.

What exactly arrives on Avalanche as AVAX?

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.

Why does the ETH to AVAX direction matter?

Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. 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?

ETH 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 ETH?

Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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.

What funds the Scroll source transaction?

ETH is the native gas asset for Scroll. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. ETH is recorded as native on this source.

What is the most dangerous wrong-network mistake here?

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

Can I swap ETH on Scroll to AVAX on Avalanche without KYC?

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