Privacy considerations for LINK to ETH
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 Base or ETH on Arbitrum activity anonymous or invisible. Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. 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. 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. 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. Token contracts, approvals, wallet reuse, recognizable amounts, close timing, and later consolidation can create association signals. Private routing changes only part of that observable transaction context. Identity-verification requirements are separate and must be checked in the live flow.
What remains visible on Base
Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. ETH is the native gas asset for Base. 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.
Base source role versus Arbitrum destination role
A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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.
Base and Arbitrum keep separate account histories
The same-looking 0x wallet syntax does not combine the two ledgers. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees. Rollup inclusion and settlement can also expose different timing milestones.
LINK approval and governance-token evidence; Native ETH gas and value 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. 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 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 Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 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. 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 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 Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
