Privacy considerations for SOL to SUI
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make SOL on Sui or SUI on Sui 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. Native SOL pays Solana fees and participates in the Solana account model. Wrapped SOL is an SPL token account representation and tokenized SOL on another network is not native SOL. 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. Token contracts, approvals, wallet reuse, recognizable amounts, close timing, and later consolidation can create association signals. Private routing changes only part of that observable transaction context. 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 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.
Sui source role versus Sui 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 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.
SOL fee-payer and account evidence; SUI coin-object evidence
Native SOL balance changes, fee-payer accounts, signatures, and later token-account activity remain visible on Solana. Tokenized SOL elsewhere follows a separate contract ledger. 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. Those source events remain public. 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 receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object. 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 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 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.
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. 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. 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.
