Swap WBTC on Ethereum to USDC on Hyperliquid (HyperEVM)

FromEthereum
ToHyperliquid
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 Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. 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 USDC

USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. The destination wallet must support the exact Hyperliquid (HyperEVM) representation. The route converts a wrapped-asset source into a stablecoin balance; the destination ticker alone is not a contract check.

USDC output identity and receiving

USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Hyperliquid (HyperEVM). The Hyperliquid (HyperEVM) side is contract-tracked rather than a native gas balance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Hyperliquid (HyperEVM) destination execution

Hyperliquid (HyperEVM) is a L1 EVM network in the Hyperliquid ecosystem. HYPE pays destination-side network gas on Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance.

Ethereum source execution

Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Ethereum. EVM 0x account address An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.

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 Ethereum. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Mistakes specific to WBTC Ethereum to USDC Hyperliquid (HyperEVM)

Route-specific mistakes include sending on a network other than Ethereum; using a destination that is not valid for Hyperliquid (HyperEVM); running out of ETH 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. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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 receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Private Route for WBTC → USDC

Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Ethereum to USDC on Hyperliquid (HyperEVM) 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; confirm the destination is HyperEVM; it does not hide either chain's public records.

  • Reduces the obvious link between the WBTC deposit and USDC receipt
  • Compare standard and Private Route options for Ethereum → Hyperliquid (HyperEVM)
  • Shows what remains public on Ethereum and Hyperliquid (HyperEVM) before you deposit
Check Private Route availability →

Related routes

Swap WBTC on Ethereum to USDC on Hyperliquid (HyperEVM) FAQs

What exactly leaves Ethereum as WBTC?

WBTC is a contract representation on Ethereum at 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599. ETH, not WBTC, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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 Hyperliquid (HyperEVM) as USDC?

USDC is a contract representation on Hyperliquid (HyperEVM) at 0xb88339cb7199b77e23db6e890353e22632ba630f. HYPE, not USDC, pays gas unless both symbols are the same. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Why does the WBTC to USDC 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 wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

What changes between the source and destination asset roles?

WBTC is the deposited wrapped-asset input; USDC 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. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Which stablecoin contract must this route match?

USDC must match the quoted Hyperliquid (HyperEVM) 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. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance.

Can I swap WBTC on Ethereum to USDC on Hyperliquid without KYC?

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