Privacy considerations for ETH to WETH
Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make ETH on Hyperliquid (HyperEVM) or WETH on Polygon activity anonymous or invisible. 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. Polygon exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Polygon PoS uses an EVM sidechain architecture with its own validator checkpoints and gas balance. Its token representations and bridge behavior are separate from Ethereum L1 even when wallets use the same 0x account. ETH is native gas on Ethereum and several rollups, but each network maintains a separate ETH balance and transaction history. A contract-wrapped form is not the native gas balance. WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. Wrapped assets depend on a token contract and a separate underlying asset model. Wrapper interactions, approvals, unwrap activity, and the destination representation can remain public and may create additional association points. Identity-verification requirements are separate and must be checked in the live flow.
What remains visible on Hyperliquid (HyperEVM)
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. HYPE is the native gas asset for Hyperliquid (HyperEVM). Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.
What remains visible on Polygon
Polygon exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Polygon PoS uses an EVM sidechain architecture with its own validator checkpoints and gas balance. Its token representations and bridge behavior are separate from Ethereum L1 even when wallets use the same 0x account. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.
Hyperliquid (HyperEVM) source role versus Polygon destination role
A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. Those source-side events remain visible. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. That receipt and later destination activity remain visible.
Hyperliquid (HyperEVM) and Polygon keep separate account histories
The same-looking 0x wallet syntax does not combine the two ledgers. 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 Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
Wrapper activity can add another association point
Wrapped-token approvals, transfers, and later unwrap activity are public contract events. 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
Native ETH gas and value evidence; WETH wrapper and unwrap 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. Those source events remain public. WETH approvals, wrapper transfers, and later unwrap activity remain visible contract events. A private route does not turn WETH into an unrecorded native ETH balance. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. The receipt and later destination use remain public.
What Private Route changes—and what it does not
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. 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 Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
Verification and provider policy for this exact route
Verification status is determined by the exact provider route, asset representations, amount, region, and current risk policy. Private, no-account, non-custodial, and no-KYC remain separate properties. 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 Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
