Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap SUI on Sui to AVAX on Avalanche

FromSui
ToAvalanche
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.
AVAX / USD
Price
—
24h
—
High
—
Low
—
Vol
—

What you need to know

Sui to Avalanche: object and account boundary

A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. Sui and Avalanche 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.

SUI input versus AVAX output representation

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

Mistakes specific to SUI Sui to AVAX Avalanche

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Avalanche; running out of SUI before the source transaction is submitted; assuming other and evm addresses are interchangeable. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

SUI input identity and handling

Sui is classified as a native asset for this route. SUI uses a native asset on Sui. The Sui side is contract-tracked rather than a native gas balance. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model.

AVAX output identity and receiving

Avalanche is classified as a native asset for this route. AVAX uses a native asset on Avalanche. The recorded Avalanche representation uses 18 decimal places. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

Private Route for SUI → AVAX

Sui account, object, transaction-effect, and fee activity remain public, and Avalanche wallet, token-transfer, contract, log, and gas activity remain public. For this SUI on Sui to AVAX on Avalanche path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Sui hexadecimal account address with an object-based asset model and destination-side EVM 0x account address; it does not hide either chain's public records.

  • ✓Reduces the obvious link between the SUI deposit and AVAX receipt
  • ✓Compare standard and Private Route options for Sui → Avalanche
  • ✓Shows what remains public on Sui and Avalanche before you deposit
Check Private Route availability →

Related routes

No-KYC and verification rulesPrivate SUI to AVAX route explainerPrivacy limits and live availabilitySwap AVAX to SUIReverse routeSui (SUI)Avalanche (AVAX)Sui networkAvalanche networkBrowse supported swap routes

Swap SUI on Sui to AVAX on Avalanche FAQs

How does the Sui coin-object side differ from the other network?

Sui uses Move coin types and objects with SUI gas. The other side follows EVM execution, so addresses and token identifiers are not interchangeable.

What exactly leaves Sui as SUI?

SUI is listed as the native representation on Sui; SUI is used for network gas. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model.

What exactly arrives on Avalanche as AVAX?

AVAX is listed as the native representation on Avalanche; AVAX is used for network gas. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

Why does the SUI to AVAX direction matter?

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. On receipt, Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

What changes between the source and destination asset roles?

SUI is the deposited native-asset input; AVAX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending SUI?

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.

What funds the Sui source transaction?

SUI is the native gas asset for Sui. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. SUI is recorded as native on this source.

Can I swap SUI on Sui to AVAX on Avalanche without KYC?

Requirements are checked for the live SUI Sui to AVAX Avalanche 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 →