POL (ex-MATIC) is classified as a governance or utility token for this route. POL uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules.
Hyperliquid (HyperEVM) is a L1 EVM network in the Hyperliquid ecosystem. HYPE pays destination-side network gas on Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM 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.
Hyperliquid is classified as a native asset for this route. HYPE uses a native asset on Hyperliquid (HyperEVM). Native HYPE exists on one recorded origin network; other network forms require representation checks. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Ethereum. EVM 0x account address An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.
Ethereum and Hyperliquid (HyperEVM) can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Route-specific mistakes include sending on a network other than Ethereum; using a destination that is not valid for Hyperliquid (HyperEVM); running out of ETH before the source transaction is submitted. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. 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 receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public. For this POL on Ethereum to HYPE on Hyperliquid (HyperEVM) path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; confirm the destination is HyperEVM; it does not hide either chain's public records.
POL is a contract representation on Ethereum at 0x455e53cbb86018ac2b8092fdcd39d8444affc3f6. ETH, not POL, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules.
HYPE is listed as the native representation on Hyperliquid (HyperEVM); HYPE is used for network gas. 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 receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. On receipt, Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
POL is the deposited token input; HYPE is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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 receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
ETH is the native gas asset for Ethereum. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. POL is token-tracked and can need approval before transfer.
Sending POL on a network other than Ethereum, or using an address that is not valid for Hyperliquid (HyperEVM), can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live POL Ethereum to HYPE Hyperliquid 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.
