Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap DAI on Base to SUI on Sui

FromBase
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

Base to Sui: object and account boundary

A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Base 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 SUI 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 SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

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 Base to SUI Sui

Route-specific mistakes include sending on a network other than Base; using a destination that is not valid for Sui; running out of ETH before the source transaction is submitted; assuming evm and other addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 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 Base. The recorded Base 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 native asset on Sui. The Sui side is contract-tracked rather than a native gas balance. 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

Base wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this DAI on Base to SUI on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x 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 SUI receipt
  • ✓Compare standard and Private Route options for Base → Sui
  • ✓Shows what remains public on Base and Sui before you deposit
Check Private Route availability →

Related routes

No-KYC and verification rulesPrivate DAI to SUI route explainerPrivacy limits and live availabilitySwap SUI to DAIReverse routeDai (DAI)Sui (SUI)Base networkSui networkBrowse supported swap routes

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

What exactly leaves Base as DAI?

DAI is a contract representation on Base with 18 decimals at 0x50c5725949A6F0c72E6C4a641F24049A917DB0Cb. ETH, not DAI, pays gas unless both symbols are the same. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 SUI?

SUI is listed as the native representation on Sui; SUI is used for network gas. 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 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 Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Which stablecoin contract must this route match?

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

Can I swap DAI on Base to SUI on Sui without KYC?

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