Privacy considerations for ETH to WBTC
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make ETH on Optimism or WBTC on zkSync Era activity anonymous or invisible. Optimism exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. OP Mainnet is an OP Stack optimistic rollup with sequenced L2 execution and Ethereum settlement. Its canonical withdrawal model has different timing from ordinary L2 inclusion, and OP Mainnet token contracts are distinct from Ethereum and other OP Stack chains. 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. ETH is native gas on Ethereum and several rollups, but each network maintains a separate ETH balance and transaction history. A contract-wrapped form is not the native gas balance. 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. 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 Optimism
Optimism exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. OP Mainnet is an OP Stack optimistic rollup with sequenced L2 execution and Ethereum settlement. Its canonical withdrawal model has different timing from ordinary L2 inclusion, and OP Mainnet token contracts are distinct from Ethereum and other OP Stack chains. ETH is the native gas asset for Optimism. 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.
Optimism source role versus zkSync Era destination role
An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. 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.
Optimism and zkSync Era keep separate account histories
The same-looking 0x wallet syntax does not combine the two ledgers. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. Rollup inclusion and settlement can also expose different timing milestones.
Wrapper activity can add another association point
Wrapped-token approvals, transfers, and later unwrap activity are public contract events. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Native ETH gas and value evidence; WBTC custody-wrapper evidence
Native ETH can expose both transfer value and gas funding on the selected network. Rollup balances, Ethereum L1 balances, and WETH contracts remain separate public records. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. Those source events remain public. 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 arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path. The receipt and later destination use remain public.
What Private Route changes—and what it does not
Private routing can reduce an obvious link between two EVM accounts, but source approvals, gas, logs, destination contract or native receipt, and later activity remain on separate chain histories. Sequencer and settlement timing can add correlation evidence. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Verification and provider policy for this exact route
The provider must support the exact L2 direction, asset contracts, amount, and region. Rollup support and privacy routing do not imply that identity verification, account, or custody requirements are absent. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
