Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap WBTC on Hyperliquid (HyperEVM) to USDC on Sui

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

Hyperliquid (HyperEVM) to Sui: object and account boundary

A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Hyperliquid (HyperEVM) and Sui use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.

Sui coin-object and SUI gas requirements

SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Coin objects and Move types are not EVM token contracts.

WBTC input versus USDC output representation

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

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 Sui representation. The route converts a wrapped-asset source into a stablecoin balance; the destination ticker alone is not a contract check.

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 Sui

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Sui; running out of HYPE before the source transaction is submitted; assuming evm and other addresses are interchangeable; 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

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.

USDC output identity and receiving

USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Sui. The Sui 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.

Private Route for WBTC → USDC

Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this WBTC on Hyperliquid (HyperEVM) to USDC on Sui 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 Sui hexadecimal account address with an object-based asset model; 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) → Sui
  • ✓Shows what remains public on Hyperliquid (HyperEVM) and Sui before you deposit
Check Private Route availability →

Related routes

No-KYC and verification rulesPrivate WBTC to USDC route explainerPrivacy limits and live availabilitySwap USDC to WBTCReverse routeWrapped Bitcoin (WBTC)USDC (USDC)Hyperliquid (HyperEVM) networkSui networkBrowse supported swap routes

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

How does the Sui coin-object side differ from the other network?

Sui uses Move coin types and objects with SUI gas. The other side follows EVM execution, so addresses and token identifiers are not interchangeable.

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 Sui as USDC?

USDC is a contract representation on Sui at 0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC. SUI, not USDC, pays gas unless both symbols are the same. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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 Sui representation. A ticker or target price is not enough to identify a token contract.

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

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