Privacy considerations for WBTC 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 WBTC on Sui or WETH on BNB Chain 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. BNB Chain exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. BNB Smart Chain uses EVM execution with BEP-20 token contracts and BNB for gas. A BEP-20 deposit is not an ERC-20 deposit even when the ticker and 0x address syntax look familiar. WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. 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 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 BNB Chain
BNB Chain exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. BNB Smart Chain uses EVM execution with BEP-20 token contracts and BNB for gas. A BEP-20 deposit is not an ERC-20 deposit even when the ticker and 0x address syntax look familiar. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Sui source role versus BNB Chain 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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
WBTC custody-wrapper evidence; WETH wrapper and unwrap evidence
WBTC approvals, wrapper-contract transfers, custodian-linked mint or burn context, and later unwrap activity remain public. No native Bitcoin UTXO is hidden by a WBTC token transfer. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. 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
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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
