Swap SOL to SUI

FromSolana
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

SOL input identity and handling

Solana is classified as a native asset for this route. SOL uses a quote-selected representation. Native SOL exists on one recorded origin network; other network forms require representation checks. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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 SOL to SUI

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

SOL source handling versus SUI receipt

Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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

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

Private Route for SOL → SUI

Solana account, token, program, signature, and fee activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this SOL on Solana to SUI on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Base58-encoded Solana 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 SOL deposit and SUI receipt
  • Compare standard and Private Route options for Solana → Sui
  • Shows what remains public on Solana and Sui before you deposit
Check Private Route availability →

Related routes

Swap SOL to SUI FAQs

Why does the SOL to SUI direction matter?

Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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?

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

Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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 SOL on Solana to SUI on Sui without KYC?

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