Swap ETH on Hyperliquid (HyperEVM) to BNB on Arbitrum

FromHyperliquid
ToArbitrum
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.
BNB / 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 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 Arbitrum L2

Hyperliquid (HyperEVM) source execution occurs on L1, while Arbitrum 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.

Arbitrum destination execution

Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Arbitrum. EVM 0x account address An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately.

BNB output identity and receiving

BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 18 decimal places. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

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 Arbitrum 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 BNB Arbitrum

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Arbitrum; running out of HYPE before the source transaction is submitted. 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. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Private Route for ETH → BNB

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

Related routes

Swap ETH on Hyperliquid (HyperEVM) to BNB on Arbitrum 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 Arbitrum as BNB?

BNB is a contract representation on Arbitrum with 18 decimals at 0x20865e63B111B2649ef829EC220536c82C58ad7B. ETH, not BNB, pays gas unless both symbols are the same. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Why does the ETH to BNB 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 BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

What changes between the source and destination asset roles?

ETH is the deposited native-asset input; BNB 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 HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

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.

What is the most dangerous wrong-network mistake here?

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

Can I swap ETH on Hyperliquid to BNB on Arbitrum without KYC?

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