Swap DAI on Solana to SOL on 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.
SOL / USD
Price
24h
High
Low
Vol

What you need to know

Solana to Sui: object and account boundary

A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Solana 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.

DAI input versus SOL output representation

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. 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.

Converting stablecoin DAI into SOL

DAI is a crypto-backed dollar-oriented stablecoin whose canonical and bridged contracts vary by network. Its peg design does not make two network representations interchangeable. The source is a stablecoin contract or recorded native representation, while SOL is classified as native-asset. Check the quoted output rather than assuming a one-dollar source unit fixes the destination amount.

Mistakes specific to DAI Solana to SOL Sui

Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Sui; running out of SOL before the source transaction is submitted; assuming solana and other addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. 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.

DAI input identity and handling

Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical.

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.

Private Route for DAI → SOL

Solana account, token, program, signature, and fee activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this DAI on Solana to SOL 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 DAI deposit and SOL 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 DAI on Solana 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 SVM execution, so addresses and token identifiers are not interchangeable.

What exactly leaves Solana as DAI?

DAI is a contract representation on Solana with 8 decimals at EjmyN6qEC1Tf1JxiG1ae7UTJhUxSwk1TCWNWqxWV4J6o. SOL, not DAI, pays gas unless both symbols are the same. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical.

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 DAI to SOL direction matter?

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. 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?

DAI is the deposited stablecoin 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 DAI?

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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.

Which stablecoin contract must this route match?

DAI must match its Solana representation. A ticker or target price is not enough to identify a token contract.

Can I swap DAI on Solana to SOL on Sui without KYC?

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