Bridge USDC from Hyperliquid (HyperEVM) to 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.

Direction

Hyperliquid → Solana

Asset

USDC

Source gas

HYPE

Destination gas

SOL

How the Sasquatch deposit route works

1. Select the source

Choose the USDC asset and Hyperliquid network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Solana 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

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. USDC uses USDC contract token on the source; USDC uses USDC contract token on Solana.

Solana token-account check for USDC

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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. A compatible wallet may create or use an associated token account, and SOL—not USDC 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). USDC is contract-tracked and can require an allowance before transfer. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs.

USDC keeps its ticker while changing ledgers

USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Hyperliquid (HyperEVM). The Hyperliquid (HyperEVM) side is contract-tracked rather than a native gas balance. Native USDC exists on one recorded origin network; other network forms require representation checks. The dollar-oriented ticker does not make USDC contracts interchangeable across networks. USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Solana. The Solana side is contract-tracked rather than a native gas balance. Native USDC exists on one recorded origin network; other network forms require representation checks. The dollar-oriented ticker does not make USDC contracts interchangeable across networks. USDC leaves as a network-specific contract asset. USDC arrives as a network-specific contract asset.

Hyperliquid (HyperEVM) to Solana bridge mistakes

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; selecting a stablecoin by ticker without checking its network contract. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Private Route for USDC → USDC

Hyperliquid wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this USDC on Hyperliquid to USDC 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 USDC deposit and USDC receipt
  • Compare standard and Private Route options for Hyperliquid → Solana
  • Shows what remains public on Hyperliquid and Solana before you deposit
Check Private Route availability →

Related routes

Hyperliquid to Solana FAQs

Can the Hyperliquid (HyperEVM) 0x account be reused as the Solana destination?

No. Base58-encoded Solana account address HYPE pays the EVM source transaction, while SOL is used for later Solana activity.

What USDC representation leaves Hyperliquid (HyperEVM)?

USDC is a contract representation on Hyperliquid (HyperEVM) at 0xb88339cb7199b77e23db6e890353e22632ba630f. HYPE, not USDC, pays gas unless both symbols are the same. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.

What USDC representation arrives on Solana?

USDC is a contract representation on Solana at EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v. SOL, not USDC, 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Does the same USDC ticker guarantee the same ledger form?

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

Which gas balances matter for this bridge?

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

What destination address should be used?

Base58-encoded Solana account address Do not substitute a Hyperliquid (HyperEVM) address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge USDC from Hyperliquid to Solana without KYC?

Requirements are checked for the live USDC Hyperliquid to 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 bridge FAQs →