Privacy considerations for WETH to LINK
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make WETH on Linea or LINK on zkSync Era activity anonymous or invisible. Linea exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge EVM rollup that batches execution and proves state to Ethereum. L2 transaction inclusion, proof completion, and Ethereum settlement are different stages, while token contracts remain specific to Linea. 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. WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. LINK is an oracle-network utility token represented by network-specific contracts. It is not the gas asset on Ethereum or EVM rollups, and bridged LINK contracts require separate verification. 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 Linea
Linea exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge EVM rollup that batches execution and proves state to Ethereum. L2 transaction inclusion, proof completion, and Ethereum settlement are different stages, while token contracts remain specific to Linea. ETH is the native gas asset for Linea. 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.
Linea source role versus zkSync Era destination role
A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. 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.
Linea and zkSync Era keep separate account histories
The same-looking 0x wallet syntax does not combine the two ledgers. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later. 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. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
WETH wrapper and unwrap evidence; LINK approval and governance-token evidence
WETH approvals, wrapper transfers, and later unwrap activity remain visible contract events. A private route does not turn WETH into an unrecorded native ETH balance. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. Those source events remain public. Token allowances, contract transfers, voting or utility interactions, source gas, and later wallet consolidation can remain visible for this receipt. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later. 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. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
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. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
