Solana uses Solana accounts and SOL for source fees, while Hyperliquid (HyperEVM) uses an EVM 0x account and HYPE for destination gas. Confirm the destination token contract and do not paste a Solana address into the EVM destination field. AVAX is read from its Solana mint or native account, while WBTC arrives at the quoted Hyperliquid (HyperEVM) native or contract representation.
Base58-encoded Solana account address SOL is the native gas asset for Solana. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. The mint/account selected by the quote must match the source wallet balance.
EVM 0x account address; confirm the destination is HyperEVM HYPE is the native gas asset for Hyperliquid (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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. A Solana address cannot receive this EVM-side output.
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 destination token on Hyperliquid (HyperEVM). Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Hyperliquid (HyperEVM); running out of SOL before the source transaction is submitted; assuming solana and evm addresses are interchangeable; treating a wrapped token as the native gas asset. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
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 arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Solana account, token, program, signature, and fee activity remain public, and Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Solana to WBTC on Hyperliquid (HyperEVM) path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Base58-encoded Solana account address and destination-side EVM 0x account address; confirm the destination is HyperEVM; it does not hide either chain's public records.
No. EVM 0x account address; confirm the destination is HyperEVM The WBTC output belongs to the quoted EVM representation.
SOL pays source fees on Solana. HYPE pays later transactions on Hyperliquid (HyperEVM); the delivered WBTC does not replace that gas balance unless it is the native asset.
AVAX is a contract representation on Solana with 8 decimals at KgV1GvrHQmRBY8sHQQeUKwTm2r2h8t4C8qt12Cw1HVE. SOL, not AVAX, pays gas unless both symbols are the same. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
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 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. On receipt, WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
AVAX is the deposited native-asset input; WBTC is the quoted wrapped-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Requirements are checked for the live AVAX Solana to WBTC 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.
