Swap WBTC on Hyperliquid (HyperEVM) to DAI on Linea

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

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.

Receiving stablecoin DAI

DAI is a crypto-backed dollar-oriented stablecoin whose canonical and bridged contracts vary by network. Its peg design does not make two network representations interchangeable. The destination wallet must support the exact Linea representation. The route converts a wrapped-asset source into a stablecoin balance; the destination ticker alone is not a contract check.

From Hyperliquid (HyperEVM) L1 into Linea L2

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

DAI output identity and receiving

Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Linea. The recorded Linea representation uses 18 decimal places. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

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.

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.

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.

Mistakes specific to WBTC Hyperliquid (HyperEVM) to DAI Linea

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Linea; running out of HYPE before the source transaction is submitted; selecting a stablecoin by ticker without checking its network contract; 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. 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. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Private Route for WBTC → DAI

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

Related routes

Swap WBTC on Hyperliquid (HyperEVM) to DAI on Linea 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 Linea as DAI?

DAI is a contract representation on Linea with 18 decimals at 0x4AF15ec2A0BD43Db75dd04E62FAA3B8EF36b00d5. ETH, not DAI, 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. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Why does the WBTC to DAI 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, The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

What changes between the source and destination asset roles?

WBTC is the deposited wrapped-asset input; DAI is the quoted stablecoin 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. 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. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Which stablecoin contract must this route match?

DAI must match the quoted Linea representation. A ticker or target price is not enough to identify a token contract.

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

Can I swap WBTC on Hyperliquid to DAI on Linea without KYC?

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