Private WETH Sui to BNB Chain Bridge

FromSui
ToBNB Chain
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

What you need to know

Privacy for the Sui to BNB Chain direction

Where offered, Private Route is intended to reduce an obvious direct association between the Sui sending wallet and BNB Chain receiving wallet; it does not hide either blockchain. SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model BNB is the native gas asset for BNB Chain. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.

Sui source-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 source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.

BNB Chain destination-side visibility

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. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.

Sui deposit role versus BNB Chain receipt role

A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Those deposit-side events remain public. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. The receipt and later activity remain public.

WETH wrapper and unwrap evidence; WETH wrapper and unwrap 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. The source transfer remains 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 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 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 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 status is separate from privacy status

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. 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 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.

Private Route for WETH → WETH

Sui account, object, transaction-effect, and fee activity remain public, and BNB Chain wallet, token-transfer, contract, log, and gas activity remain public. For this WETH on Sui to WETH on BNB Chain path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Sui hexadecimal account address with an object-based asset model and destination-side EVM 0x account address; it does not hide either chain's public records.

  • Reduces the obvious link between the WETH deposit and WETH receipt
  • Compare standard and Private Route options for Sui → BNB Chain
  • Shows what remains public on Sui and BNB Chain before you deposit
Check Private Route availability →

Related routes

Private WETH Sui to BNB Chain Bridge FAQs

What must be verified for a private WETH Sui to BNB Chain bridge?

Check the exact WETH representations, live privacy status, provider, amount, region, source gas, destination address, fees, and any verification request. Standard bridge support is not proof of private availability.

Which Sui bridge records remain public?

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 deposit, gas funding, representation, confirmations, amount, and sending-address history remain observable.

Which BNB Chain records remain public after receipt?

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. Delivery and later activity remain observable even if the provider path reduces direct wallet association.

Which WETH events remain visible on this private bridge?

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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. Both the deposit and receipt remain ledger records.

Does private Sui to BNB Chain bridging guarantee no KYC?

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. 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 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.

View all Help Center FAQs →