Privacy considerations for WBTC 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 WBTC on Scroll or BNB on Solana 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. 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. 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. 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 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 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.
Scroll source role versus Solana 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 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.
EVM deposit and Solana receipt create different public records
Scroll records the 0x source account, gas, approvals, and token transfer. Solana records the destination account keys, token-account changes, programs, fees, and signature. Private routing can change the direct provider path without making either ecosystem invisible.
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. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
WBTC custody-wrapper evidence; BNB native and token representation 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. 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 a direct association between the EVM deposit account and Solana receiving account. The 0x transaction, approval, gas, Solana signature, token-account changes, amounts, and timing remain public evidence. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that 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.
