Review HYPE network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
Hyperliquid (HYPE)
Type
Native asset
Available networks
3
Native networks
Hyperliquid (HyperEVM)
Route support
Available
HYPE is the native gas asset used by HyperEVM in this route inventory. HYPE is the native gas asset for HyperEVM in this inventory. HyperEVM HYPE must be distinguished from balances or positions represented in other Hyperliquid environments.
HYPE is recorded as native on Hyperliquid (HyperEVM). Native status describes the ledger balance and gas behavior on that network, not every token carrying the ticker.
Contract forms are recorded on Hyperliquid L1, Solana. Each form needs its own address, wallet, and network check.
Hyperliquid (HyperEVM) (native), Hyperliquid L1 (contract), Solana (contract)
The contract representations currently share one recorded decimal format, but contract identity and network still require independent verification.
Confirm that the destination is HyperEVM rather than a different Hyperliquid environment. Do not mix HyperEVM requirements with Hyperliquid L1 or HyperCore behavior. Native HYPE and token representations on other networks are not interchangeable.
ARB → HYPE, AVAX → HYPE, BNB → HYPE, BTC → HYPE, DAI → HYPE, DOGE → HYPE, ETH → HYPE, LINK → HYPE, OP → HYPE, POL → HYPE
HYPE → ARB, HYPE → AVAX, HYPE → BNB, HYPE → BTC, HYPE → DAI, HYPE → DOGE, HYPE → ETH, HYPE → LINK, HYPE → OP, HYPE → POL
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.
HYPE is recorded as native on Hyperliquid (HyperEVM). Other listed forms can be contract or provider-mapped representations.
No. Native status belongs to the recorded origin network; another chain's HYPE-labelled token maintains separate balances and transaction history.
Hyperliquid (HyperEVM), Hyperliquid L1, Solana
Sasquatch currently lists routes for Hyperliquid. Exact availability still depends on the selected networks and live quote.
Confirm that the destination is HyperEVM rather than a different Hyperliquid environment. Do not mix HyperEVM requirements with Hyperliquid L1 or HyperCore behavior.
