Privacy considerations for WETH to ARB
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 Polygon or ARB on Arbitrum activity anonymous or invisible. Polygon exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Polygon PoS uses an EVM sidechain architecture with its own validator checkpoints and gas balance. Its token representations and bridge behavior are separate from Ethereum L1 even when wallets use the same 0x account. Arbitrum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Its Nitro optimistic-rollup design executes through a sequencer and posts compressed transaction data to Ethereum. L2 inclusion and Ethereum settlement are separate milestones, so a source receipt can advance before the rollup state is final on L1. 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. ARB is a governance token and does not pay Arbitrum transaction gas; ETH remains the gas asset. A bridged ARB contract on another network is a separate representation from the Arbitrum token. 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 Polygon
Polygon exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Polygon PoS uses an EVM sidechain architecture with its own validator checkpoints and gas balance. Its token representations and bridge behavior are separate from Ethereum L1 even when wallets use the same 0x account. POL is the native gas asset for Polygon. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
What remains visible on Arbitrum
Arbitrum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Its Nitro optimistic-rollup design executes through a sequencer and posts compressed transaction data to Ethereum. L2 inclusion and Ethereum settlement are separate milestones, so a source receipt can advance before the rollup state is final on L1. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Polygon source role versus Arbitrum destination role
A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Those source-side events remain visible. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. That receipt and later destination activity remain visible.
Polygon and Arbitrum keep separate account histories
The same-looking 0x wallet syntax does not combine the two ledgers. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement. 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
WETH wrapper and unwrap evidence; ARB 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement. 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 Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
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 Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
