HyperEVM wallet setup: RPC, chain ID, gas and transfers

Official HyperEVM network settings

HyperEVM can be added as a custom EVM network in wallets such as MetaMask or Rabby. Verify each field against the official documentation rather than accepting an unsolicited add-network prompt.

A block explorer is optional and independent from the RPC. An explorer displaying a transaction does not certify that the contract or token is safe.

1. Open MetaMask or Rabby and select Add Custom Network.
2. Enter Hyperliquid as the network name.
3. Enter https://rpc.hyperliquid.xyz/evm as the RPC URL.
4. Enter 999 as the chain ID.
5. Enter HYPE as the currency symbol.
6. Optionally add https://hyperevmscan.io/ or https://www.hyperscan.com/ as the block explorer.
7. Save the network, switch to Hyperliquid and confirm that the wallet shows chain ID 999 before you sign.

Network name  Hyperliquid
Chain ID      999
Currency      HYPE
RPC           https://rpc.hyperliquid.xyz/evm

Move assets between HyperCore and HyperEVM

The official app exposes EVM ↔ Core transfer controls from the balances or portfolio view. Each supported spot asset has its own transfer path, and fees are paid in HYPE on the environment initiating the move.

The address 0x2222222222222222222222222222222222222222 is a special transfer path for HYPE only. Sending another asset to it can permanently lose that asset. Prefer the official asset-specific interface.

Why HyperEVM gas can spike

HyperEVM uses an EIP-1559-style fee market. Demand for limited blockspace can raise base and priority fees. HyperCore trading being gasless does not make HyperEVM contract calls gasless.

Keep a small HYPE buffer, inspect estimated gas and contract intent, and avoid signing an unlimited approval merely to solve a failed transaction.

External bridges add another trust boundary

The official onboarding page lists several independent bridges and swaps, but those services are not the same as the native Core–EVM transfer. Their contracts, relayers, supported assets, fees and recovery paths differ.

Confirm source chain, destination chain 999, token contract and minimums. Test first and verify that any centralized exchange explicitly supports HyperEVM rather than only HYPE on HyperCore.

Frequently asked questions