Privacy considerations for USDC 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 USDC on Scroll or BNB on zkSync Era activity anonymous or invisible. Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. 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. 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. 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. Stablecoins can exist through different contracts and issuers on different networks. Confirm the exact representation and remember that contract events, issuer controls, receiving services, and later transfers can add context beyond the immediate swap. Identity-verification requirements are separate and must be checked in the live flow.
What remains visible on Scroll
Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. ETH is the native gas asset for Scroll. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
What remains visible on zkSync Era
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. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Scroll source role versus zkSync Era destination role
A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. Those source-side events remain visible. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. That receipt and later destination activity remain visible.
Scroll and zkSync Era keep separate account histories
The same-looking 0x wallet syntax does not combine the two ledgers. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token. Rollup inclusion and settlement can also expose different timing milestones.
Stablecoin contracts add representation and issuer context
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. Source contract events remain visible. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token. Issuer controls, receiving-service deposits, and later transfers can provide context beyond the immediate route.
USDC native, canonical, or bridged evidence; BNB native and token representation 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. 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 wallet association, but stablecoin contract events, issuer context, provider observations, source gas, destination receipt, amounts, timing, and later transfers remain visible. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. 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
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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
