Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Bridge USDC from Hyperliquid (HyperEVM) to Sui

FromHyperliquid
ToSui
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 → Sui

Asset

USDC

Source gas

HYPE

Destination gas

SUI

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 Sui 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

Hyperliquid (HyperEVM) to Sui: object and account boundary

A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Hyperliquid (HyperEVM) and Sui use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.

Sui coin-object and SUI gas requirements

SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Coin objects and Move types are not EVM token contracts.

USDC input versus USDC output representation

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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

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 Sui. The Sui 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 Sui bridge mistakes

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Sui; running out of HYPE before the source transaction is submitted; assuming evm and other 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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 Sui account, object, transaction-effect, and fee activity remain public. For this USDC on Hyperliquid to USDC on Sui 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 Sui hexadecimal account address with an object-based asset model; 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 → Sui
  • ✓Shows what remains public on Hyperliquid and Sui before you deposit
Check Private Route availability →

Related routes

Private USDC from Hyperliquid to Sui route explainerPrivacy limits and live availabilityNo-KYC and verification rulesProvider and region requirementsCan a bridge link source and destination wallets?FAQ answerWhat is cross-chain privacy?FAQ answerCan USDC transactions be traced?FAQ answerCan bridge transactions be traced?Privacy researchPrivate bridge security checklistPrivacy researchHow cross-chain transactions are trackedPrivacy research

Hyperliquid to Sui FAQs

Which side uses Sui coin objects and SUI gas?

Sui is the Sui side. Its Move coin types, address, objects, and SUI gas do not transfer as EVM contract metadata.

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 Sui?

USDC is a contract representation on Sui at 0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC. SUI, not USDC, pays gas unless both symbols are the same. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. The bridge output does not automatically fund every later gas need.

What destination address should be used?

Sui hexadecimal account address with an object-based asset model 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 Sui can prevent normal detection or receipt.

Can I bridge USDC from Hyperliquid to Sui without KYC?

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