Swap AVAX to SUI

FromAvalanche
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.
SUI / USD
Price
24h
High
Low
Vol

What you need to know

AVAX input identity and handling

Avalanche is classified as a native asset for this route. AVAX uses a quote-selected representation. Native AVAX exists on one recorded origin network; other network forms require representation checks. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.

SUI output identity and receiving

Sui is classified as a native asset for this route. SUI uses a quote-selected representation. Native SUI exists on one recorded origin network; other network forms require representation checks. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Mistakes specific to AVAX to SUI

Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.

AVAX source handling versus SUI receipt

On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Representation transition for this direction

AVAX leaves as a quote-selected representation. SUI arrives as a quote-selected representation.

Private Route for AVAX → SUI

Avalanche wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this AVAX on Avalanche to SUI on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address 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 AVAX deposit and SUI receipt
  • Compare standard and Private Route options for Avalanche → Sui
  • Shows what remains public on Avalanche and Sui before you deposit
Check Private Route availability →

Related routes

Swap AVAX to SUI FAQs

Why does the AVAX to SUI direction matter?

On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. On receipt, Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

What changes between the source and destination asset roles?

AVAX is the deposited native-asset input; SUI 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 AVAX?

On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. Match the source network shown by the quote. Confirm the destination network in the quote. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

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

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