Main.netChain settings lookup

Chain profile

HyperEVM chain ID 999 and mainnet RPC URL

Source snapshot

Source evidence snapshot July 4, 2026. HyperEVM is the EVM environment connected to Hyperliquid. Hyperliquid documentation lists chain ID 999, RPC URL https://rpc.hyperliquid.xyz/evm, HYPE as gas token, and HyperEVM explorer options.

Quick settings

HyperEVM RPC status and chain ID answer

HyperEVM mainnet uses chain ID 999 / 0x3e7, RPC URL https://rpc.hyperliquid.xyz/evm, explorer https://hyperevmscan.io, and HYPE as the gas token. Use the latest source check and linked docs to verify the fields before adding the network to a wallet, script, or app.

Chain ID
999 / 0x3e7
RPC URL
https://rpc.hyperliquid.xyz/evm
Explorer
https://hyperevmscan.io
Gas token
HYPE
Source docs
Hyperliquid docs
Latest check
Jul 4, 2026
Source snapshot
July 4, 2026
Config path
wallet_addEthereumChain JSON

Copy HyperEVM configOpen source docsExplorer directoryGas token directory

Good fit when you need:
  • the HyperEVM chain ID, RPC URL, explorer, and gas token in one place;
  • source documentation links beside the copied setup fields;
  • manual wallet config fields without connecting a wallet or choosing an RPC provider.
Before you paste these fields:
  • compare the chain ID against the source link on this page;
  • open the explorer once and confirm it matches the network you expect;
  • use the public RPC for setup checks, then choose monitored infrastructure for production traffic.
Chain ID999 / 0x3e7
RPC URLhttps://rpc.hyperliquid.xyz/evm
Explorerhttps://hyperevmscan.io
Gas tokenHYPE
VerificationVerified metadata
Metadata labelJuly 4, 2026
Evidence snapshot

Verification record

Manual metadata review and automated evidence checks are tracked separately. This is not a live uptime, latency, or production reliability monitor.

Manual metadata review
Verification status
Verified metadata
Verification run
source-monitoring-2026-07-04
Verification tool
source-monitoring-refresh
Source set
Hyperliquid docs
Manual review cadence
monthly; after August 3, 2026
Latest recorded chain ID probe
eth_chainId matched expected 0x3e7; observed 0x3e7 on

MethodologyReport a correction

HyperEVM wallet-add fields

Wallet directory sites often expose a connect button. Main.net keeps the same MetaMask and EIP-3085 setup fields as text so developers can compare them with official/source docs before calling wallet_addEthereumChain.

chainId
0x3e7 (999)
chainName
HyperEVM
nativeCurrency
HYPE; name HYPE, symbol HYPE, decimals 18
rpcUrls
https://rpc.hyperliquid.xyz/evm
blockExplorerUrls
https://hyperevmscan.io
GlossaryChain IDHow wallet and RPC software identify a mainnet network.GlossaryRPC endpointWhat an RPC URL does and why public endpoints can be rate-limited.GlossaryMainnetThe production network context for these chain settings.Gas tokenHYPE gas tokenOther mainnet rows that use HYPE for gas.Network categoryEVM mainnetsCompare HyperEVM with related evm mainnets by chain ID, RPC URL, explorer, and source links.GuideChain ID listChain IDs, RPC URLs, explorers, and source links across Main.net.

Monitoring evidence

These checks are review signals only. They are not uptime, latency, privacy, or production reliability claims.

Snapshot generated
Source checks
3 sources checked
Source changes
0 changes since the previous source hash snapshot
Source fetch failures
0
eth_chainId probe
matched expected 0x3e7
Per-source check timing
Included in the monitoring snapshot, not used as this page's review date

View monitoring snapshots orsource change history.

Network endpoints

Primary public RPC
https://rpc.hyperliquid.xyz/evm
Explorer
https://hyperevmscan.io
Official/source documentation
Hyperliquid docs
Chain type
Hyperliquid EVM mainnet
Chain ID hex
0x3e7
Manual review cadence
monthly; next review after August 3, 2026

HyperEVM common questions

What is the HyperEVM mainnet RPC URL?
HyperEVM's listed primary public RPC URL is https://rpc.hyperliquid.xyz/evm.
What is HyperEVM's chain ID?
HyperEVM's listed chain ID is 999.
What block explorer does HyperEVM use?
HyperEVM's listed block explorer is https://hyperevmscan.io.
What gas token does HyperEVM use?
HyperEVM's listed gas token is HYPE.

Copy-ready config

Neutral app configuration built from the verified fields above. Copy buttons only place text on your clipboard; they do not connect a wallet, request permissions, or rank RPC providers.

Chain ID decimal999
Chain ID hex0x3e7
RPC URLhttps://rpc.hyperliquid.xyz/evm
Explorer URLhttps://hyperevmscan.io
EIP-3085-shaped JSON

Rendered as text for manual review before use.

{
  "chainId": "0x3e7",
  "chainName": "HyperEVM",
  "nativeCurrency": {
    "name": "HYPE",
    "symbol": "HYPE",
    "decimals": 18
  },
  "rpcUrls": [
    "https://rpc.hyperliquid.xyz/evm"
  ],
  "blockExplorerUrls": [
    "https://hyperevmscan.io"
  ]
}

Developer snippets

Static examples generated from Main.net fields. These snippets are for manual configuration review and read-only RPC checks; they do not connect wallets, create signers, submit writes, or rank providers.

ts

viem chain definition

Read-only snippet generated from Main.net fields. Review official sources before production use.

import { defineChain } from 'viem'

export const hyperevmMainnet = defineChain({
  id: 999,
  name: "HyperEVM",
  nativeCurrency: {
    name: "HYPE",
    symbol: "HYPE",
    decimals: 18,
  },
  rpcUrls: {
    default: { http: ["https://rpc.hyperliquid.xyz/evm"] },
    public: { http: ["https://rpc.hyperliquid.xyz/evm"] },
  },
  blockExplorers: {
    default: {
      name: "hyperevmscan.io",
      url: "https://hyperevmscan.io",
    },
  },
})
ts

wagmi read-only config

Read-only transport example generated from Main.net fields. It does not include account adapters or transaction actions.

import { createConfig, http } from 'wagmi'
import { hyperevmMainnet } from './hyperevm'

export const config = createConfig({
  chains: [hyperevmMainnet],
  transports: {
    [hyperevmMainnet.id]: http("https://rpc.hyperliquid.xyz/evm"),
  },
})
ts

ethers read-only provider

Read-only JsonRpcProvider example generated from Main.net fields. It does not create a signer.

import { JsonRpcProvider } from 'ethers'

export const provider = new JsonRpcProvider("https://rpc.hyperliquid.xyz/evm", {
  chainId: 999,
  name: "hyperevm",
})

const network = await provider.getNetwork()
console.log(network.chainId)
bash

curl eth_chainId check

Minimal JSON-RPC identity check. This verifies the endpoint-reported chain ID only, not uptime or production suitability.

curl -s -X POST \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
  https://rpc.hyperliquid.xyz/evm

# Expected chain ID: 999 / 0x3e7

Developer signals

External dashboards a developer may inspect before choosing where to deploy. Main.net links to these references but does not collect the metric values, normalize methodologies, rank chains, or recommend deployments.

explorerHyperEVM explorerExplorer-hosted blocks, transactions, contracts, token transfers, and verification tools from the listed explorer.

Source links

HyperEVM wallet setupHyperEVM developer notesChainID.network 999 conflict

Safety note

Chain ID 999 has a registry conflict: Hyperliquid documents HyperEVM mainnet, while ChainID.network lists Wanchain Testnet. Verify the source and wallet prompt before sending funds.

Main.net is an independent reference site. It does not operate this chain, custody assets, execute transactions, or provide investment advice.

Report a correction

If this page has stale RPC, explorer, chain ID, or source information, open a public correction issue with a source link so it can be checked.

Report HyperEVM dataSend page feedback