Swap DAI on Scroll to SUI on Solana

FromScroll
ToSolana
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

Convert the Scroll 0x input into a Solana-account receipt

Scroll uses EVM account addresses and ETH for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. DAI uses DAI contract token on the source; SUI uses SUI contract token on Solana.

Solana token-account check for SUI

Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object. A compatible wallet may create or use an associated token account, and SOL—not SUI unless it is SOL—pays later Solana fees.

Scroll approval and gas before the handoff

ETH is the native gas asset for Scroll. DAI is contract-tracked and can require an allowance before transfer. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently.

Converting stablecoin DAI into SUI

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 SUI 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 Scroll to SUI Solana

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Solana; running out of ETH before the source transaction is submitted; assuming evm and solana addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

DAI input identity and handling

Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Scroll. The recorded Scroll representation uses 18 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.

SUI output identity and receiving

Sui is classified as a native asset for this route. SUI uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Private Route for DAI → SUI

Scroll wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this DAI on Scroll to SUI on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana account address; it does not hide either chain's public records.

  • Reduces the obvious link between the DAI deposit and SUI receipt
  • Compare standard and Private Route options for Scroll → Solana
  • Shows what remains public on Scroll and Solana before you deposit
Check Private Route availability →

Related routes

Swap DAI on Scroll to SUI on Solana FAQs

Can a Scroll 0x address receive SUI on Solana?

No. The destination must be a Solana-compatible address. Base58-encoded Solana account address

Does receiving SUI create a Solana token account?

An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.

What exactly leaves Scroll as DAI?

DAI is a contract representation on Scroll with 18 decimals at 0xcA77eB3fEFe3725Dc33bccB54eDEFc3D9f764f97. ETH, not DAI, pays gas unless both symbols are the same. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 Solana as SUI?

SUI is a contract representation on Solana with 8 decimals at suifhC9gU1VbJAPYPTBkHJyyyStKGLLYPVDTmPoqbvA. SOL, not SUI, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Why does the DAI to SUI 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 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?

DAI is the deposited stablecoin 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 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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 DAI on Scroll to SUI on Solana without KYC?

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