Privacy for the Hyperliquid (HyperEVM) to Linea direction
Where offered, Private Route is intended to reduce an obvious direct association between the Hyperliquid (HyperEVM) sending wallet and Linea 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 Linea. 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.
Linea destination-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 destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Hyperliquid (HyperEVM) deposit role versus Linea 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. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. The receipt and later activity remain public.
Two EVM histories can still be compared
Hyperliquid (HyperEVM) and Linea 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.
Native ETH gas and value evidence; Native ETH gas and value evidence
Native ETH can expose both transfer value and gas funding on the selected network. Rollup balances, Ethereum L1 balances, and WETH contracts remain separate public records. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. The source transfer remains public. Native ETH can expose both transfer value and gas funding on the selected network. Rollup balances, Ethereum L1 balances, and WETH contracts remain separate public records. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees. 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. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
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. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
