EVM-to-EVM execution boundary
Hyperliquid (HyperEVM) and Polygon can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Direction
Hyperliquid → Polygon
Asset
USDC
Source gas
HYPE
Destination gas
POL
Choose the USDC asset and Hyperliquid network you currently hold.
Check the estimated output, fees, timing, and Polygon destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Hyperliquid (HyperEVM) and Polygon can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Hyperliquid (HyperEVM) is a L1 EVM network in the Hyperliquid ecosystem. HYPE pays source-side network gas on Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs.
EVM 0x account address POL is the native gas asset for Polygon. The quote identifies whether the delivered asset is native, contract-based, or bridged.
Polygon is a L1 EVM network in the Polygon ecosystem. POL pays destination-side network gas on Polygon. EVM 0x account address A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.
Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for Polygon; running out of HYPE before the source transaction is submitted. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.

Hyperliquid wallet, token-transfer, contract, log, and gas activity remain public, and Polygon wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Hyperliquid to USDC on Polygon path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address; confirm the destination is HyperEVM and destination-side EVM 0x account address; it does not hide either chain's public records.
The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit Polygon output before depositing.
A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. The bridge output does not automatically fund every later gas need.
EVM 0x account address Do not substitute a Hyperliquid (HyperEVM) address merely because a wallet displays both networks.
Sending on a network other than Hyperliquid (HyperEVM), selecting a representation not listed by the quote, or entering an address invalid for Polygon can prevent normal detection or receipt.
Requirements are checked for the live USDC Hyperliquid to Polygon quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.