Swap HYPE on Hyperliquid (HyperEVM) to WBTC on Solana

FromHyperliquid
ToSolana
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

What you need to know

Convert the Hyperliquid (HyperEVM) 0x input into a Solana-account receipt

Hyperliquid (HyperEVM) uses EVM account addresses and HYPE for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. HYPE uses native HYPE on the source; WBTC uses WBTC wrapped token on Solana.

Solana token-account check for WBTC

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. 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 compatible wallet may create or use an associated token account, and SOL—not WBTC unless it is SOL—pays later Solana fees.

Hyperliquid (HyperEVM) approval and gas before the handoff

HYPE is the native gas asset for Hyperliquid (HyperEVM). HYPE is a native source balance. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs.

WBTC wrapped-token output check

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 Solana. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Mistakes specific to HYPE Hyperliquid (HyperEVM) to WBTC Solana

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Solana; running out of HYPE before the source transaction is submitted; assuming evm and solana addresses are interchangeable; 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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 input identity and handling

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.

WBTC output identity and receiving

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Solana. The Solana side is contract-tracked rather than a native gas 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.

Private Route for HYPE → WBTC

Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this HYPE on Hyperliquid (HyperEVM) to WBTC on Solana 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 Base58-encoded Solana account address; it does not hide either chain's public records.

  • Reduces the obvious link between the HYPE deposit and WBTC receipt
  • Compare standard and Private Route options for Hyperliquid (HyperEVM) → Solana
  • Shows what remains public on Hyperliquid (HyperEVM) and Solana before you deposit
Check Private Route availability →

Related routes

Swap HYPE on Hyperliquid (HyperEVM) to WBTC on Solana FAQs

Can a Hyperliquid (HyperEVM) 0x address receive WBTC on Solana?

No. The destination must be a Solana-compatible address. Base58-encoded Solana account address

Does receiving WBTC create a Solana token account?

An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.

What exactly leaves Hyperliquid (HyperEVM) as HYPE?

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.

What exactly arrives on Solana as WBTC?

WBTC is a contract representation on Solana at 5XZw2LKTyrfvfiskJ78AMpackRjPcyCif1WhUsPDuVqQ. SOL, not WBTC, 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. 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.

Why does the HYPE to WBTC direction matter?

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.

What changes between the source and destination asset roles?

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.

What should be matched before sending HYPE?

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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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.

Can I swap HYPE on Hyperliquid to WBTC on Solana without KYC?

Requirements are checked for the live HYPE Hyperliquid to WBTC 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.

View all Help Center FAQs →