Privacy for the Optimism to Arbitrum direction
Where offered, Private Route is intended to reduce an obvious direct association between the Optimism sending wallet and Arbitrum receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Optimism. EVM 0x account address ETH is the native gas asset for Arbitrum. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Optimism source-side visibility
Optimism exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. OP Mainnet is an OP Stack optimistic rollup with sequenced L2 execution and Ethereum settlement. Its canonical withdrawal model has different timing from ordinary L2 inclusion, and OP Mainnet token contracts are distinct from Ethereum and other OP Stack chains. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Arbitrum destination-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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Optimism deposit role versus Arbitrum receipt role
An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. Those deposit-side events remain public. 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. The receipt and later activity remain public.
Two EVM histories can still be compared
Optimism and Arbitrum 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.
USDC issuer and contract context
USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. Both bridge sides can expose contract events, amounts, receiving services, and later transfers; a stable target value does not make those records private or interchangeable.
USDC native, canonical, or bridged evidence; USDC native, canonical, or bridged evidence
The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. The source transfer remains public. The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. The destination receipt and later use remain public even when direct wallet association is reduced.
Cross-chain linkability limits
Private routing can reduce direct wallet association, but stablecoin contract events, issuer context, provider observations, source gas, destination receipt, amounts, timing, and later transfers remain visible. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
Verification status is separate from privacy status
The live provider evaluates the exact stablecoin contract or native label, counter-asset, amount, region, and current policy. Issuer controls and provider identity checks are separate, and neither is waived by Private Route. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
