Where offered, Private Route is intended to reduce an obvious direct association between the Arbitrum sending wallet and Base 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 Base. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
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.
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. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.
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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. The receipt and later activity remain public.
Arbitrum and Base 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.
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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.
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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Arbitrum to USDC on Base path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.
Check the exact source and destination asset representations, live privacy status, provider, amount, region, source gas, destination address, fees, and any verification request. Standard bridge support is not proof of private availability.
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 deposit, gas funding, representation, confirmations, amount, and sending-address history remain observable.
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. Delivery and later activity remain observable even if the provider path reduces direct wallet association.
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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.
