Swap WBTC on Hyperliquid (HyperEVM) to OP on Optimism

FromHyperliquid
ToOptimism
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.
OP / USD
Price
24h
High
Low
Vol

What you need to know

WBTC input identity and handling

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Hyperliquid (HyperEVM). The recorded Hyperliquid (HyperEVM) representation uses 8 decimal places. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

From Hyperliquid (HyperEVM) L1 into Optimism L2

Hyperliquid (HyperEVM) source execution occurs on L1, while Optimism 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 unwrap or exchange input 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 source token on Hyperliquid (HyperEVM). Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Optimism destination execution

Optimism is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Optimism. EVM 0x account address An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance.

OP output identity and receiving

Optimism is classified as a governance or utility token for this route. OP uses a network-specific contract asset on Optimism. The Optimism side is contract-tracked rather than a native gas balance. OP receipt is a governance-token balance, not destination gas. Verify the destination contract and keep ETH available for OP Mainnet activity.

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 Optimism 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 WBTC Hyperliquid (HyperEVM) to OP Optimism

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Optimism; 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance. OP receipt is a governance-token balance, not destination gas. Verify the destination contract and keep ETH available for OP Mainnet activity.

Private Route for WBTC → OP

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

Related routes

Swap WBTC on Hyperliquid (HyperEVM) to OP on Optimism FAQs

What exactly leaves Hyperliquid (HyperEVM) as WBTC?

WBTC is a contract representation on Hyperliquid (HyperEVM) with 8 decimals at 0x0555E30da8f98308EdB960aa94C0Db47230d2B9c. HYPE, not WBTC, 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

What exactly arrives on Optimism as OP?

OP is a contract representation on Optimism at 0x4200000000000000000000000000000000000042. ETH, not OP, pays gas unless both symbols are the same. An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance. OP receipt is a governance-token balance, not destination gas. Verify the destination contract and keep ETH available for OP Mainnet activity.

Why does the WBTC to OP direction matter?

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. On receipt, OP receipt is a governance-token balance, not destination gas. Verify the destination contract and keep ETH available for OP Mainnet activity.

What changes between the source and destination asset roles?

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

What should be matched before sending WBTC?

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance. OP receipt is a governance-token balance, not destination gas. Verify the destination contract and keep ETH available for OP Mainnet activity.

Can the wrapped asset pay native network gas?

No. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. An OP Mainnet receipt belongs to the OP Stack L2 and needs ETH on that network for later activity; it is not an Ethereum L1 balance.

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. WBTC is token-tracked and can need approval before transfer.

Can I swap WBTC on Hyperliquid to OP on OP Mainnet without KYC?

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