Privacy considerations for SUI to WETH
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 Solana or WETH on Base activity anonymous or invisible. 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. Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. 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. WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. Wrapped assets depend on a token contract and a separate underlying asset model. Wrapper interactions, approvals, unwrap activity, and the destination representation can remain public and may create additional association points. Identity-verification requirements are separate and must be checked in the live flow.
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. SOL is the native gas asset for Solana. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
What remains visible on Base
Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Solana source role versus Base destination role
A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Those source-side events remain visible. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. That receipt and later destination activity remain visible.
Solana source activity and EVM delivery remain inspectable
Solana exposes the source signature, accounts, mint or native balance changes, programs, and SOL fee. Base exposes the destination 0x account, token contract or native receipt, logs, and later gas funding.
Wrapper activity can add another association point
Wrapped-token approvals, transfers, and later unwrap activity are public contract events. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
SUI coin-object evidence; WETH wrapper and unwrap 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. WETH approvals, wrapper transfers, and later unwrap activity remain visible contract events. A private route does not turn WETH into an unrecorded native ETH balance. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. The receipt and later destination use remain public.
What Private Route changes—and what it does not
Private routing can reduce a direct association between the Solana source account and EVM receiver. The source signature, program and token-account changes, destination contract logs, gas, amounts, and timing remain public. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native SUI is selected from Sui coin objects and can fund gas; tokenized SUI outside Sui does not use the object model. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
