Privacy for the Scroll to Hyperliquid (HyperEVM) direction
Where offered, Private Route is intended to reduce an obvious direct association between the Scroll sending wallet and Hyperliquid (HyperEVM) receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Scroll. 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.
Scroll source-side visibility
Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. 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.
Scroll deposit role versus Hyperliquid (HyperEVM) receipt role
A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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
Scroll 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.
USDT issuer and contract context
USDT is issued through ERC-20, TRC-20, SPL, and other network-specific contracts. The ticker does not determine the token standard, contract, issuer controls, or destination address model. 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.
USDT token-standard evidence; USDT token-standard evidence
ERC-20, TRC-20, SPL, and other USDT representations expose different contract or token-account events. Issuer controls, receiving services, amount, timing, and later transfers can add context to this deposit. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. The source transfer remains public. ERC-20, TRC-20, SPL, and other USDT representations expose different contract or token-account events. Issuer controls, receiving services, amount, timing, and later transfers can add context to this receipt. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another. 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. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. 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. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
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. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. 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. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
