Bridge WBTC from Solana to Hyperliquid (HyperEVM)

FromSolana
ToHyperliquid
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.

Direction

Solana → Hyperliquid

Asset

WBTC

Source gas

SOL

Destination gas

HYPE

How the Sasquatch deposit route works

1. Select the source

Choose the WBTC asset and Solana network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Hyperliquid destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

Move from a Solana account into Hyperliquid (HyperEVM) EVM

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. WBTC is read from its Solana mint or native account, while WBTC arrives at the quoted Hyperliquid (HyperEVM) native or contract representation.

WBTC mint and SOL fee checks

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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. The mint/account selected by the quote must match the source wallet balance.

Hyperliquid (HyperEVM) contract and 0x receiving checks

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 keeps its ticker while changing ledgers

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. 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. The Hyperliquid (HyperEVM) side is contract-tracked rather than a native gas balance. WBTC leaves as a wrapped contract asset. WBTC arrives as a wrapped contract asset.

Solana to Hyperliquid (HyperEVM) bridge mistakes

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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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.

Private Route for WBTC → WBTC

Solana account, token, program, signature, and fee activity remain public, and Hyperliquid wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Solana to WBTC on Hyperliquid 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.

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

Related routes

Solana to Hyperliquid FAQs

What changes between the Solana source and Hyperliquid (HyperEVM) receipt?

The source uses a Solana signature, mint or native account, and SOL fees. The destination uses a 0x account, HYPE gas, and the quoted EVM token contract or native balance.

What WBTC representation leaves Solana?

WBTC is a contract representation on Solana at 5XZw2LKTyrfvfiskJ78AMpackRjPcyCif1WhUsPDuVqQ. SOL, not WBTC, 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

What WBTC representation arrives on Hyperliquid (HyperEVM)?

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.

Does the same WBTC ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a WBTC wrapped token and a WBTC wrapped token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

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. The bridge output does not automatically fund every later gas need.

What destination address should be used?

EVM 0x account address; confirm the destination is HyperEVM Do not substitute a Solana address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Solana, selecting a representation not listed by the quote, or entering an address invalid for Hyperliquid (HyperEVM) can prevent normal detection or receipt.

Can I bridge WBTC from Solana to Hyperliquid without KYC?

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

View all bridge FAQs →