Swap ETH on Hyperliquid (HyperEVM) to WBTC on Scroll

FromHyperliquid
ToScroll
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.

What you need to know

ETH input identity and handling

Ethereum is classified as a native asset for this route. ETH uses a network-specific contract asset on Hyperliquid (HyperEVM). The recorded Hyperliquid (HyperEVM) 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.

From Hyperliquid (HyperEVM) L1 into Scroll L2

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

WBTC wrapped-token output check

WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. On this route WBTC is the destination token on Scroll. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Scroll destination execution

Scroll is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Scroll. EVM 0x account address A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll.

WBTC output identity and receiving

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Scroll. The recorded Scroll representation uses 8 decimal places. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Hyperliquid (HyperEVM) source execution

Hyperliquid (HyperEVM) is a L1 EVM network in the Hyperliquid ecosystem. HYPE pays source-side network gas on Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs.

EVM-to-EVM execution boundary

Hyperliquid (HyperEVM) and Scroll 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 Hyperliquid (HyperEVM) to WBTC Scroll

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Scroll; running out of HYPE before the source transaction is submitted; treating a wrapped token as the native gas asset. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. 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 receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Private Route for ETH → WBTC

Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public, and Scroll wallet, token-transfer, contract, log, and gas activity remain public. For this ETH on Hyperliquid (HyperEVM) to WBTC on Scroll path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address; confirm the destination is HyperEVM 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 WBTC receipt
  • Compare standard and Private Route options for Hyperliquid (HyperEVM) → Scroll
  • Shows what remains public on Hyperliquid (HyperEVM) and Scroll before you deposit
Check Private Route availability →

Related routes

Swap ETH on Hyperliquid (HyperEVM) to WBTC on Scroll FAQs

What exactly leaves Hyperliquid (HyperEVM) as ETH?

ETH is a contract representation on Hyperliquid (HyperEVM) with 18 decimals at 0x1fbcCdc677c10671eE50b46C61F0f7d135112450. HYPE, not ETH, pays gas unless both symbols are the same. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. 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 Scroll as WBTC?

WBTC is a contract representation on Scroll with 8 decimals at 0x3C1BCa5a656e69edCD0D4E36BEbb3FcDAcA60Cf1. ETH, not WBTC, pays gas unless both symbols are the same. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Why does the ETH to WBTC 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, WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

What changes between the source and destination asset roles?

ETH is the deposited native-asset input; WBTC is the quoted wrapped-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 HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Can the wrapped asset pay native network gas?

No. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll.

What funds the Hyperliquid (HyperEVM) source transaction?

HYPE is the native gas asset for Hyperliquid (HyperEVM). A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. ETH is token-tracked and can need approval before transfer.

Can I swap ETH on Hyperliquid to WBTC on Scroll without KYC?

Requirements are checked for the live ETH Hyperliquid to WBTC Scroll 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 →