Privacy for the Hyperliquid (HyperEVM) to Arbitrum direction
Where offered, Private Route is intended to reduce an obvious direct association between the Hyperliquid (HyperEVM) sending wallet and Arbitrum receiving wallet; it does not hide either blockchain. HYPE is the native gas asset for Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM 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.
Hyperliquid (HyperEVM) source-side visibility
Hyperliquid (HyperEVM) exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. HyperEVM is the smart-contract execution environment represented here and uses HYPE for gas. HyperEVM addresses must not be confused with HyperCore balances, vault actions, or other Hyperliquid account conventions. 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.
Hyperliquid (HyperEVM) deposit role versus Arbitrum receipt role
A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. 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
Hyperliquid (HyperEVM) 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.
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. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. 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.
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. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. 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.
