HyperEVM RPC and chain settings

Hyperliquid is one chain with two parts. HyperCore is the exchange (order books, margin, liquidations) and has its own API (beginner’s guide). The HyperEVM is an Ethereum-compatible smart-contract environment built into the same chain and secured by the same consensus (HyperCore vs HyperEVM). Anything that speaks Ethereum JSON-RPC (MetaMask, Rabby, Foundry, Hardhat, viem, ethers) works with the HyperEVM once you give it the settings below.

Network settings

Setting	Mainnet	Testnet
Network name	HyperEVM	HyperEVM Testnet
Chain ID	999 (0x3e7)	998 (0x3e6)
RPC URL	https://rpc.hyperliquid.xyz/evm	https://rpc.hyperliquid-testnet.xyz/evm
Currency symbol	HYPE (18 decimals)	HYPE (18 decimals)
Block explorer	https://hyperevmscan.io	not listed in the docs

Chain IDs and RPCs are from the HyperEVM docs. On 4 November 2026 at 20:45 UTC we checked them live:

curl -s https://rpc.hyperliquid.xyz/evm \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

{"jsonrpc":"2.0","id":1,"result":"0x3e7"}

The testnet RPC answered 0x3e6. Mainnet eth_blockNumber returned 0x300f582 (block 50,394,498). eth_gasPrice returned 0x78e3c7f, about 0.127 gwei, and it moves with demand.

What the public RPC supports

The rpc.hyperliquid.xyz/evm endpoint is fine for testing and light use. Its limits, from the JSON-RPC docs and the rate limits page:

• 100 requests per minute per IP. Hyperliquid’s docs point out that other providers have “more sophisticated rate limiting logic and archive node functionality”.
• Latest block only for eth_call, eth_estimateGas, eth_getBalance, eth_getCode, eth_getStorageAt and eth_getTransactionCount. Historical-state requests are not supported on the default RPC.
• eth_getLogs: at most 50 blocks per query and up to 4 topics. Indexers need an archive provider or their own node.
• No WebSocket JSON-RPC (eth_subscribe) on this endpoint (HyperEVM docs).
• eth_maxPriorityFeePerGas always returns 0 (we got 0x0), and eth_syncing always returns false.
• Custom methods: eth_bigBlockGasPrice, eth_usingBigBlocks, and eth_getSystemTxsByBlockHash / eth_getSystemTxsByBlockNumber, which return the system transactions that come from HyperCore.

Hyperliquid’s tools page lists other RPC and archive providers, including Alchemy, Chainstack, dRPC, Dwellir, HypurrScan, QuickNode and Stakely (HyperEVM tools). We haven’t benchmarked them. Check each provider’s own limits.

Gas, blocks and fees

• HYPE is the gas token. The HyperEVM runs the Cancun hardfork without blobs, with EIP-1559 on. Base fees are burned, and unlike most EVM chains, priority fees are burned too (HyperEVM docs).
• Two block types. Small blocks come every 1 second with a 3M gas limit. Big blocks come every 1 minute with a 30M gas limit (dual-block architecture). The latest block we read had a 3,000,000 gas limit.
• Deploying a big contract? It may not fit in 3M gas. Send the HyperCore action {"type":"evmUserModify","usingBigBlocks":true} so your address’s transactions go to big blocks, and price them with eth_bigBlockGasPrice. It answered 0x5f5e100 (0.1 gwei) on 4 November. Switch back afterwards: the flag stays on until you unset it. The Python SDK has use_big_blocks() for this.
• Mempool rules. The onchain mempool accepts only the next 8 nonces per address, and drops transactions older than a day.

Moving HYPE and tokens between HyperCore and HyperEVM

Your HyperCore address and HyperEVM address are the same 0x…, but the balances are separate (transfers):

• HYPE: send it to 0x2222222222222222222222222222222222222222 on either side. On the EVM it arrives as native gas, not an ERC-20.
• Other linked tokens: each has its own system address, 0x20 followed by the token index in big-endian, e.g. 0x20000000000000000000000000000000000000c8 for token 200. Don’t send a token to the HYPE address. It’s lost.
• Wrapped HYPE (WHYPE) is a WETH-style system contract at 0x5555555555555555555555555555555555555555. Its symbol() returned WHYPE on 4 November (wrapped HYPE).
• A Core-to-EVM transfer costs 200k gas at the next block’s base price.

Step-by-step for users: move funds between HyperCore and HyperEVM.

Reading and writing HyperCore from a contract

A HyperEVM contract can read HyperCore state, such as positions, balances and oracle prices, through read precompiles starting at 0x…0800. It can send HyperCore actions, such as orders, transfers and staking, through the CoreWriter contract at 0x3333333333333333333333333333333333333333. Our explainer covers both, with addresses and gas costs: CoreWriter and precompiles.

Two things catch contract developers out:

• Activation fee. A new HyperCore account costs 1 quote token (1 USDC, for example) the first time something is sent to it. Until a contract’s address is activated on HyperCore, it can’t send CoreWriter actions (activation gas fee).
• Error code 10055 means an error at the boundary between HyperCore and HyperEVM: a nonce error, insufficient funds, a duplicate transaction hash or an underpriced replacement (HyperEVM docs).

Explorers

Hyperliquid’s docs list these HyperEVM explorers (HyperEVM tools):

Explorer	URL	Notes
HyperEVMScan	hyperevmscan.io	By Etherscan
Hyperscan	hyperscan.com	Blockscout-based
Owlscan	owlscan.org

HyperEVM explorers don’t show HyperCore trades. For trades, fills and transfers on the exchange, use the explorer built into the official app or HypurrScan.

Testnet

• RPC and chain: https://rpc.hyperliquid-testnet.xyz/evm, chain ID 998. HyperCore testnet API: https://api.hyperliquid-testnet.xyz.
• Testnet HYPE for gas: Chainstack’s faucet gives 1 HYPE every 24 hours. QuickNode runs one too (both listed in HyperEVM tools).
• Testnet USDC: Hyperliquid’s own faucet gives 1,000 mock USDC, but only to addresses that have deposited on mainnet (testnet faucet).
• Asset IDs differ between networks. HYPE is token 150 on mainnet and 1105 on testnet (asset IDs). Don’t hard-code mainnet IDs in testnet code.

Is the RPC slow or down right now? Hyperliquid status checks the latest HyperEVM block and the HyperCore API from your browser every 60 seconds.