Privacy for the zkSync Era to BNB Chain direction
Where offered, Private Route is intended to reduce an obvious direct association between the zkSync Era sending wallet and BNB Chain receiving wallet; it does not hide either blockchain. ETH is the native gas asset for zkSync Era. EVM 0x account address 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.
zkSync Era source-side visibility
zkSync Era exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge rollup using EraVM and native account-abstraction features while settling proofs to Ethereum. Execution, fee estimation, and contract compatibility can differ from a byte-for-byte Ethereum assumption. 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.
zkSync Era deposit role versus BNB Chain receipt role
A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. 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.
Two EVM histories can still be compared
zkSync Era and BNB Chain use separate chain identifiers, balances, contracts, transaction hashes, and gas records even when address syntax matches. Sequencer inclusion and settlement timing can add further observable milestones.
USDC issuer and contract context
USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. Both bridge sides can expose contract events, amounts, receiving services, and later transfers; a stable target value does not make those records private or interchangeable.
USDC native, canonical, or bridged evidence; USDC native, canonical, or bridged evidence
The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. The source transfer remains public. The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. The destination receipt and later use remain public even when direct wallet association is reduced.
Cross-chain linkability limits
Private routing can reduce direct wallet association, but stablecoin contract events, issuer context, provider observations, source gas, destination receipt, amounts, timing, and later transfers remain visible. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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 wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
Verification status is separate from privacy status
The live provider evaluates the exact stablecoin contract or native label, counter-asset, amount, region, and current policy. Issuer controls and provider identity checks are separate, and neither is waived by Private Route. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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 wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
