Privacy for the Arbitrum to Ethereum direction
Where offered, Private Route is intended to reduce an obvious direct association between the Arbitrum sending wallet and Ethereum receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Arbitrum. EVM 0x account address ETH is the native gas asset for Ethereum. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Arbitrum source-side visibility
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. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Ethereum destination-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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Arbitrum deposit role versus Ethereum receipt 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 deposit-side events remain public. 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. The receipt and later activity remain public.
Two EVM histories can still be compared
Arbitrum and Ethereum 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.
ARB approval and governance-token evidence; ARB approval and governance-token evidence
Token allowances, contract transfers, voting or utility interactions, source gas, and later wallet consolidation can remain visible for this deposit. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. The source transfer remains 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 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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
