# Canonical: https://www.uddalak.xyz/hyperliquid-academy/article/117-wallets-rpcs-explorers-hyperevm
# Author: Uddalak Das
# Last source: https://www.uddalak.xyz/hyperliquid-academy/article/117-wallets-rpcs-explorers-hyperevm

---
title: "Wallets, RPCs, and Explorers for HyperEVM"
description: "HyperEVM uses standard EVM wallet and JSON-RPC concepts, but users still need Hyperliquid-specific chain settings, reliable RPC infrastructure, and explorers that understand system transactions and cross-environment state."
pillar: "Ecosystem"
track: "Ecosystem"
cluster: "Ecosystem"
level: "Intermediate"
primary_icp: ["builder", "DeFi-native user"]
secondary_icp: []
content_type: "reference"
reading_time: "3 min"
last_reviewed: "2026-09-07"
last_verified: "2026-09-07"
volatile: true
prerequisites: ["03-hyperevm-explained"]
related: ["80-hyperliquid-l1-read-precompiles-complete-guide", "94-production-grade-hyperliquid-trading-bot"]
---

# Wallets, RPCs, and Explorers for HyperEVM

HyperEVM is EVM-compatible, so familiar wallets and developer libraries can connect using its chain ID and RPC endpoint. The surrounding infrastructure still differs from Ethereum mainnet. Hyperliquid has protocol-specific system transactions, read precompiles, CoreWriter behavior, and HyperCore state that a generic EVM explorer or RPC may not surface completely.

## Wallet configuration

Mainnet uses chain ID 999 and HYPE as native gas. Testnet uses chain ID 998. Users should add network details from current Hyperliquid documentation or a trusted wallet integration rather than copy random chain settings from social media.

## RPC choice

The default Hyperliquid RPC supports standard JSON-RPC with documented exceptions and custom endpoints. Independent providers may add archive data, WebSocket RPC, higher limits, or geographic infrastructure.

A production application should test multiple providers and define failover rather than depend on one endpoint.

## Explorer limits

An EVM explorer can show contract calls and balances but may not explain the resulting HyperCore action. System transactions and CoreWriter effects can require Hyperliquid-aware interpretation.

For debugging, combine EVM transaction data with HyperCore account and market state.

## Security

RPC providers can observe requests and influence the data returned to a client, though they cannot forge a valid signed transaction. Sensitive applications should verify critical state through redundant sources where practical.

Wallet prompts should make chain, contract, and action context clear enough that a user can distinguish a normal call from a malicious approval.

## How this connects

Start with [HyperEVM Explained](/hyperliquid-academy/article/03-hyperevm-explained) if the underlying concept is unfamiliar. Related reading: [Hyperliquid L1 Read Precompiles: Complete Guide](/hyperliquid-academy/article/80-hyperliquid-l1-read-precompiles-complete-guide), [How to Build a Production-Grade Hyperliquid Trading Bot](/hyperliquid-academy/article/94-production-grade-hyperliquid-trading-bot).

## Sources

- https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm
- https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/json-rpc
- https://hyperliquid.gitbook.io/hyperliquid-docs/hyperevm