Privacy for the Ethereum to zkSync Era direction
Where offered, Private Route is intended to reduce an obvious direct association between the Ethereum sending wallet and zkSync Era receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Ethereum. EVM 0x account address ETH is the native gas asset for zkSync Era. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Ethereum source-side visibility
Ethereum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is the settlement-layer EVM network for this inventory. ERC-20 transfers can require a separate approval, base fee and priority fee affect source cost, and an L1 token contract does not establish an L2 representation. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
zkSync Era destination-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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Ethereum deposit role versus zkSync Era receipt role
An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Those deposit-side events remain public. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. The receipt and later activity remain public.
Two EVM histories can still be compared
Ethereum and zkSync Era 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.
Native ETH gas and value evidence; Native ETH gas and value 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. The source transfer remains public. 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees. The destination receipt and later use remain public even when direct wallet association is reduced.
Cross-chain linkability limits
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 Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Verification status is separate from privacy status
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 Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
