Swap SUI on Sui to SOL on Sui

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

What you need to know

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.

SOL output identity and receiving

Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Sui. The recorded Sui representation uses 8 decimal places. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Sui source execution

Sui is a L1 Move VM network in the Sui ecosystem. SUI pays source-side network gas on Sui. Sui hexadecimal account address with an object-based asset model A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution.

Mistakes specific to SUI Sui to SOL Sui

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Sui; running out of SUI before the source transaction is submitted. 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. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

SUI source handling versus SOL receipt

Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Private Route for SUI → SOL

Sui account, object, transaction-effect, and fee activity remain public. For this SUI on Sui to SOL on Sui 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 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 SUI deposit and SOL receipt
  • Compare standard and Private Route options for Sui → Sui
  • Shows what remains public on Sui and Sui before you deposit
Check Private Route availability →

Related routes

Swap SUI on Sui to SOL on Sui 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 Move VM 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 Sui as SOL?

SOL is a contract representation on Sui with 8 decimals at 0xb7844e289a8410e50fb3ca48d69eb9cf29e27d223ef90353fe1bd8e27ff8f3f8::coin::COIN. SUI, not SOL, 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. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Why does the SUI to SOL 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 SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

What changes between the source and destination asset roles?

SUI is the deposited native-asset input; SOL 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. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

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 SOL on Sui without KYC?

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