Private USDC on Ethereum to WBTC 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 USDC to WBTC

Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make USDC on Ethereum or WBTC 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. 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. WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. 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

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. Source contract events remain visible. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. Issuer controls, receiving-service deposits, and later transfers can provide context beyond the immediate route.

Wrapper activity can add another association point

Wrapped-token approvals, transfers, and later unwrap activity are public contract events. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

USDC native, canonical, or bridged evidence; WBTC custody-wrapper evidence

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 source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. Those source events remain public. WBTC approvals, wrapper-contract transfers, custodian-linked mint or burn context, and later unwrap activity remain public. No native Bitcoin UTXO is hidden by a WBTC token transfer. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. 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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Private Route for USDC → WBTC

Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this USDC on Ethereum to WBTC 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 USDC deposit and WBTC 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 USDC on Ethereum to WBTC on Sui Swap FAQs

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

Confirm the live privacy status, provider, exact USDC source representation, WBTC 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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Which USDC 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 USDC deposit, gas funding, approval or native transfer, amount, and timing remain outside any promise of invisibility.

Which WBTC 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 WBTC receipt and later wallet activity remain observable on that ledger.

Do stablecoins create additional privacy considerations here?

Yes. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. Issuer, representation, amount, timing, and receiving-service context can remain observable.

How do USDC source records differ from WBTC receipt records?

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. Private Route does not erase either asset-specific record.

Does this private USDC to WBTC 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. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

View all Help Center FAQs →