Hyperliquid is classified as a native asset for this route. HYPE uses a native asset on Hyperliquid (HyperEVM). Native HYPE exists on one recorded origin network; other network forms require representation checks. HyperEVM HYPE can fund source gas and value, but HyperCore balances or positions are not interchangeable deposit inputs.
Hyperliquid (HyperEVM) source execution occurs on L1, while Linea delivery occurs on a separate L2 ledger that settles to ethereum. HYPE pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.
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 Linea. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Linea. EVM 0x account address A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract.
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Linea. The recorded Linea 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.
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.
Hyperliquid (HyperEVM) and Linea can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.
Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Linea; running out of HYPE before the source transaction is submitted; 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. HyperEVM HYPE can fund source gas and value, but HyperCore balances or positions are not interchangeable deposit inputs. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. 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.
Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public, and Linea wallet, token-transfer, contract, log, and gas activity remain public. For this HYPE on Hyperliquid (HyperEVM) to WBTC on Linea 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.
HYPE is listed as the native representation on Hyperliquid (HyperEVM); HYPE is used for network gas. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. HyperEVM HYPE can fund source gas and value, but HyperCore balances or positions are not interchangeable deposit inputs.
WBTC is a contract representation on Linea with 8 decimals at 0x3aAB2285ddcDdaD8edf438C1bAB47e1a9D05a9b4. ETH, not WBTC, pays gas unless both symbols are the same. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. 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.
HyperEVM HYPE can fund source gas and value, but HyperCore balances or positions are not interchangeable deposit inputs. 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.
HYPE 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.
HyperEVM HYPE can fund source gas and value, but HyperCore balances or positions are not interchangeable deposit inputs. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. 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.
No. 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 HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract.
HYPE is the native gas asset for Hyperliquid (HyperEVM). A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. HYPE is recorded as native on this source.
Requirements are checked for the live HYPE Hyperliquid to WBTC Linea 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.
