Privacy considerations for WETH to BNB
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make WETH on Sui or BNB 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. 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. BNB pays gas on BNB Smart Chain and is native within the BNB ecosystem. A BEP-20 or externally bridged BNB representation must be distinguished from BNB used directly for BSC gas. 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 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.
Wrapper activity can add another association point
Wrapped-token approvals, transfers, and later unwrap activity are public contract events. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
WETH wrapper and unwrap evidence; BNB native and token representation evidence
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 leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. Those source events remain public. BNB pays gas on BNB Smart Chain and is native within the BNB ecosystem. A BEP-20 or externally bridged BNB representation must be distinguished from BNB used directly for BSC gas. The exact receipt representation, amount, timing, and later wallet activity remain observable. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token. 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. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
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. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
