Swap WBTC on Hyperliquid (HyperEVM) to USDC on BNB Chain

FromHyperliquid
ToBNB Chain
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 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 BNB Chain 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 BNB Chain. The recorded BNB Chain representation uses 18 decimal places. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

BNB Chain destination execution

BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays destination-side network gas on BNB Chain. EVM 0x account address A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.

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 USDC BNB Chain

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for BNB Chain; 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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. 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

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

Related routes

Swap WBTC on Hyperliquid (HyperEVM) to USDC on BNB Chain 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 BNB Chain as USDC?

USDC is a contract representation on BNB Chain with 18 decimals at 0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d. BNB, not USDC, pays gas unless both symbols are the same. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. 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. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. 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 BNB Chain 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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.

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

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