Privacy for the Linea to Hyperliquid (HyperEVM) direction
Where offered, Private Route is intended to reduce an obvious direct association between the Linea sending wallet and Hyperliquid (HyperEVM) receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Linea. EVM 0x account address HYPE is the native gas asset for Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Linea source-side visibility
Linea exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge EVM rollup that batches execution and proves state to Ethereum. L2 transaction inclusion, proof completion, and Ethereum settlement are different stages, while token contracts remain specific to Linea. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Hyperliquid (HyperEVM) destination-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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Linea deposit role versus Hyperliquid (HyperEVM) receipt role
A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. Those deposit-side events remain public. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. The receipt and later activity remain public.
Two EVM histories can still be compared
Linea and Hyperliquid (HyperEVM) 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 Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance.
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 Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance.
