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 HYPE can be delivered on Solana.
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. Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Bitcoin confirmations and Solana transaction finality are separate milestones.
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for Solana; running out of BTC before the source transaction is submitted; assuming bitcoin and solana addresses are interchangeable; 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
Hyperliquid is classified as a native asset for this route. HYPE uses a network-specific contract asset on Solana. The recorded Solana representation uses 9 decimal places. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
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 Solana account, token, program, signature, and fee activity remain public. For this BTC on Bitcoin to HYPE on Solana 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 Base58-encoded Solana account address; 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees.
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.
HYPE is a contract representation on Solana with 9 decimals at 98sMhvDwXj1RQi5c5Mndm3vPe9cBqPrbLaufMXFNMh5g. SOL, not HYPE, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. On receipt, Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
BTC is the deposited native-asset input; HYPE is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Requirements are checked for the live BTC Bitcoin to HYPE Solana 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.
