Privacy considerations for LINK to WETH
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make LINK on Arbitrum or WETH on Ethereum activity anonymous or invisible. 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. 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. 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. 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. 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 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. ETH is the native gas asset for Arbitrum. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
What remains visible on Ethereum
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. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Arbitrum source role versus Ethereum destination role
On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Those source-side events remain visible. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. That receipt and later destination activity remain visible.
Arbitrum and Ethereum keep separate account histories
The same-looking 0x wallet syntax does not combine the two ledgers. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. 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. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
LINK approval and governance-token evidence; WETH wrapper and unwrap evidence
Token allowances, contract transfers, voting or utility interactions, source gas, and later wallet consolidation can remain visible for this deposit. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. Those source events remain public. 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 arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. 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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
