hyperliquid/dev-guide
Hyperliquid HyperEVM Developer Guide
hyperliquidtechnical-doc🏛️ Officialconfidence mediumhealth 100%
v1.0.0·Updated 3/30/2026
Last Updated: 2026-03-30 Source: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm
Network Information
| Parameter | Value |
|---|---|
| Mainnet Chain ID | 999 |
| EVM RPC | https://rpc.hyperliquid.xyz/evm |
| Info API | https://api.hyperliquid.xyz/info |
| Native Token | HYPE |
| Explorer | https://hypurrscan.io |
Two Core Endpoints
/evm — EVM Compatibility Layer
Standard EVM endpoint with support for ethers/viem/web3.js:
import { createPublicClient, http } from 'viem'
const hyperliquid = {
id: 999,
name: 'Hyperliquid',
nativeCurrency: { name: 'HYPE', symbol: 'HYPE', decimals: 18 },
rpcUrls: { default: { http: ['https://rpc.hyperliquid.xyz/evm'] } },
}
/info — Perps Data API
Fetch perpetual futures market data (bypasses EVM):
# Get all market information
curl -X POST https://api.hyperliquid.xyz/info \
-H "Content-Type: application/json" \
-d '{"type": "metaAndAssetCtxs"}'
# Get account positions
curl -X POST https://api.hyperliquid.xyz/info \
-d '{"type": "clearinghouseState", "user": "0x..."}'
Contract Deployment
# Deploy to HyperEVM using Foundry
forge create src/MyContract.sol:MyContract \
--rpc-url https://rpc.hyperliquid.xyz/evm \
--private-key $PRIVATE_KEY
Important Notes
- HyperEVM and the Perps engine share the same L1; contracts can directly access perps data
- Gas is paid in HYPE (note: not ETH)
- Some EVM opcode behavior differs slightly from standard EVM; recommend testing before mainnet deployment