It spends discrete UTXOs rather than debiting an account balance. Input selection creates outputs and often change, confirmation depth matters to the provider, and a native receiving address must match the Bitcoin address types accepted by the active route. The deposit is a Bitcoin transaction funded by selected inputs; BTC network fees and change outputs are part of the source record before USDC can be delivered on Hyperliquid (HyperEVM).
Native BTC is a Bitcoin UTXO asset with confirmations and Bitcoin address rules. Tokenized or wrapped Bitcoin on a smart-contract chain follows a contract ledger instead of the native UTXO graph. The live route must identify native BTC explicitly; a BTC ticker on another chain can represent a wrapped or bridged token.
The provider sets the required Bitcoin confirmation depth. 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. Bitcoin confirmations and Hyperliquid (HyperEVM) transaction finality are separate milestones.
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for Hyperliquid (HyperEVM); running out of BTC before the source transaction is submitted; assuming bitcoin and evm addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract; confusing native BTC with wrapped or tokenized Bitcoin. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. 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.
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 native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
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.
Bitcoin is classified as a UTXO-native asset for this route. BTC uses a native asset on Bitcoin. Native BTC exists on one recorded origin network; other network forms require representation checks. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations.
Bitcoin UTXO inputs, outputs, change, and confirmation history remain public, and Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public. For this BTC on Bitcoin to USDC on Hyperliquid (HyperEVM) path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats and destination-side EVM 0x account address; confirm the destination is HyperEVM; it does not hide either chain's public records.
The Bitcoin side uses native BTC and the UTXO ledger. Native BTC is a Bitcoin UTXO asset with confirmations and Bitcoin address rules. Tokenized or wrapped Bitcoin on a smart-contract chain follows a contract ledger instead of the native UTXO graph.
The provider waits for its required source confirmation depth. The account-chain transaction and the Bitcoin transaction are separate records.
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.
BTC is listed as the native representation on Bitcoin; BTC is used for network gas. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations.
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.
A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. On receipt, The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
BTC is the deposited native-asset input; USDC is the quoted stablecoin output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Requirements are checked for the live BTC Bitcoin 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.
