Privacy considerations for SUI 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 SUI on Sui or USDC on Solana activity anonymous or invisible. 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. Solana exposes account keys, transaction signatures, token-account changes, program calls, amounts, fees, and timing. It uses an account-and-program execution model with transaction signatures rather than EVM hashes. SPL tokens use mint and token-account records, and a receiving wallet may need the correct associated token account plus SOL for later activity. SUI is the native coin used for gas in Sui’s object-centric Move model. A token carrying the SUI ticker outside that object model is not a native Sui coin object. 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 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. SUI is the native gas asset for Sui. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
What remains visible on Solana
Solana exposes account keys, transaction signatures, token-account changes, program calls, amounts, fees, and timing. It uses an account-and-program execution model with transaction signatures rather than EVM hashes. SPL tokens use mint and token-account records, and a receiving wallet may need the correct associated token account plus SOL for later activity. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Sui source role versus Solana destination role
A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Those source-side events remain visible. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. That receipt and later destination activity remain visible.
Stablecoin contracts add representation and issuer context
Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. 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.
SUI coin-object evidence; USDC native, canonical, or bridged evidence
SUI coin-object changes, ownership, gas, and later Move interactions remain public on Sui. Tokenized SUI on another ledger creates a different public record. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. 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. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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
Provider policy is evaluated for the exact Solana mint or native asset, the other network representation, amount, and region. Cross-ecosystem wallet compatibility and no-KYC status are separate checks. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
