Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap SOL on Sui to DAI on Arbitrum

FromSui
ToArbitrum
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 to Arbitrum: object and account boundary

A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Sui and Arbitrum 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.

SOL input versus DAI output representation

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. 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.

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

Mistakes specific to SOL Sui to DAI Arbitrum

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Arbitrum; running out of SUI before the source transaction is submitted; assuming other and evm addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. 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.

SOL input identity and handling

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

DAI output identity and receiving

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

Sui account, object, transaction-effect, and fee activity remain public, and Arbitrum wallet, token-transfer, contract, log, and gas activity remain public. For this SOL on Sui to DAI on Arbitrum 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 EVM 0x account address; it does not hide either chain's public records.

  • ✓Reduces the obvious link between the SOL deposit and DAI receipt
  • ✓Compare standard and Private Route options for Sui → Arbitrum
  • ✓Shows what remains public on Sui and Arbitrum before you deposit
Check Private Route availability →

Related routes

No-KYC and verification rulesPrivate SOL to DAI route explainerPrivacy limits and live availabilitySwap DAI to SOLReverse routeSolana (SOL)Dai (DAI)Sui networkArbitrum networkBrowse supported swap routes

Swap SOL on Sui to DAI on Arbitrum 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 EVM execution, so addresses and token identifiers are not interchangeable.

What exactly leaves 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 source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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.

What exactly arrives on Arbitrum as DAI?

DAI is a contract representation on Arbitrum with 18 decimals at 0xDA10009cBd5D07dd0CeCc66161FC93D7c9000da1. ETH, not DAI, pays gas unless both symbols are the same. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. 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 SOL to DAI 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, 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?

SOL 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 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. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. 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.

Which stablecoin contract must this route match?

DAI must match the quoted Arbitrum representation. A ticker or target price is not enough to identify a token contract.

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

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