Swap SUI on Solana to DAI on Ethereum

FromSolana
ToEthereum
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

Move from a Solana account into Ethereum EVM

Solana uses Solana accounts and SOL for source fees, while Ethereum uses an EVM 0x account and ETH for destination gas. Confirm the destination token contract and do not paste a Solana address into the EVM destination field. SUI is read from its Solana mint or native account, while DAI arrives at the quoted Ethereum native or contract representation.

SUI mint and SOL fee checks

Base58-encoded Solana account address SOL is the native gas asset for Solana. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. The mint/account selected by the quote must match the source wallet balance.

Ethereum contract and 0x receiving checks

EVM 0x account address ETH is the native gas asset for Ethereum. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path. A Solana address cannot receive this EVM-side output.

Receiving stablecoin DAI

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 destination wallet must support the exact Ethereum representation. The route converts a native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.

Mistakes specific to SUI Solana to DAI Ethereum

Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Ethereum; running out of SOL before the source transaction is submitted; assuming solana and evm 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. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

SUI input identity and handling

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 is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model.

DAI output identity and receiving

Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Private Route for SUI → DAI

Solana account, token, program, signature, and fee activity remain public, and Ethereum wallet, token-transfer, contract, log, and gas activity remain public. For this SUI on Solana to DAI on Ethereum 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 EVM 0x account address; it does not hide either chain's public records.

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

Related routes

Swap SUI on Solana to DAI on Ethereum FAQs

Can a Solana address be used for the Ethereum output?

No. EVM 0x account address The DAI output belongs to the quoted EVM representation.

What pays gas on each side of this Solana-to-EVM route?

SOL pays source fees on Solana. ETH pays later transactions on Ethereum; the delivered DAI does not replace that gas balance unless it is the native asset.

What exactly leaves 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 source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 Ethereum as DAI?

DAI is a contract representation on Ethereum at 0x6b175474e89094c44da98b954eedeac495271d0f. ETH, not DAI, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Why does the SUI to DAI 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, The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

What changes between the source and destination asset roles?

SUI is the deposited native-asset input; DAI is the quoted stablecoin 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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Can I swap SUI on Solana to DAI on Ethereum without KYC?

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