Private DAI on Ethereum to USDC on Sui Swap

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

What you need to know

Privacy considerations for DAI to USDC

Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make DAI on Ethereum or USDC on Sui activity anonymous or invisible. Ethereum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is the settlement-layer EVM network for this inventory. ERC-20 transfers can require a separate approval, base fee and priority fee affect source cost, and an L1 token contract does not establish an L2 representation. Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. 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. USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. Stablecoins can exist through different contracts and issuers on different networks. Confirm the exact representation and remember that contract events, issuer controls, receiving services, and later transfers can add context beyond the immediate swap. Identity-verification requirements are separate and must be checked in the live flow.

What remains visible on Ethereum

Ethereum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is the settlement-layer EVM network for this inventory. ERC-20 transfers can require a separate approval, base fee and priority fee affect source cost, and an L1 token contract does not establish an L2 representation. ETH is the native gas asset for Ethereum. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.

What remains visible on Sui

Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.

Ethereum source role versus Sui destination role

An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Those source-side events remain visible. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. That receipt and later destination activity remain visible.

Stablecoin contracts add representation and issuer context

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. Source contract events remain visible. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. Destination receipt remains visible. Issuer controls, receiving-service deposits, and later transfers can provide context beyond the immediate route.

DAI collateral-token and bridge evidence; USDC native, canonical, or bridged evidence

DAI is a crypto-backed stablecoin, but each network representation has its own public contract events. Provider routing does not hide allowances, transfers, receiving addresses, or later consolidation. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. Those source events remain public. The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. The receipt and later destination use remain public.

What Private Route changes—and what it does not

Private routing can reduce direct association across Sui objects and the other ledger account. Move object changes, gas, the other-network receipt, amounts, timing, and later transfers remain public. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Verification and provider policy for this exact route

Support for the exact Sui coin type or object-side asset, other network representation, amount, and region is evaluated by the live provider. Privacy intent does not establish no-KYC status. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Private Route for DAI → USDC

Ethereum 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 Ethereum to USDC 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 USDC receipt
  • Compare standard and Private Route options for Ethereum → Sui
  • Shows what remains public on Ethereum and Sui before you deposit
Check Private Route availability →

Related routes

Private DAI on Ethereum to USDC on Sui Swap FAQs

What must be checked before using Private Route for DAI on Ethereum to USDC on Sui?

Confirm the live privacy status, provider, exact DAI source representation, USDC destination representation, amount, region, fees, address, and any verification request. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Which DAI on Ethereum records remain public?

Ethereum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is the settlement-layer EVM network for this inventory. ERC-20 transfers can require a separate approval, base fee and priority fee affect source cost, and an L1 token contract does not establish an L2 representation. The DAI deposit, gas funding, approval or native transfer, amount, and timing remain outside any promise of invisibility.

Which USDC on Sui records remain public after delivery?

Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. The USDC receipt and later wallet activity remain observable on that ledger.

Do stablecoins create additional privacy considerations here?

Yes. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. Issuer, representation, amount, timing, and receiving-service context can remain observable.

How do DAI source records differ from USDC receipt records?

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. Private Route does not erase either asset-specific record.

Does this private DAI to USDC route guarantee no KYC?

Support for the exact Sui coin type or object-side asset, other network representation, amount, and region is evaluated by the live provider. Privacy intent does not establish no-KYC status. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

View all Help Center FAQs →