Privacy for the Solana to Sui direction
Where offered, Private Route is intended to reduce an obvious direct association between the Solana sending wallet and Sui receiving wallet; it does not hide either blockchain. SOL is the native gas asset for Solana. Base58-encoded Solana account address SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Solana source-side visibility
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. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Sui destination-side visibility
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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Solana deposit role versus Sui receipt role
A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Those deposit-side events remain public. 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 receipt and later activity remain public.
SOL fee-payer and account evidence; SOL fee-payer and account 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. The source transfer remains public. 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 receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native. The destination receipt and later use remain public even when direct wallet association is reduced.
Cross-chain linkability limits
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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
Verification status is separate from privacy status
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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
