Hyperliquid RPC Endpoints

Dwellir provides Hyperliquid HyperEVM endpoints for mainnet (Chain ID 999). Contact Dwellir for endpoint URLs and API key access. Replace <your-api-key> with the key from your Dwellir dashboard.

Yes. Dwellir provides WebSocket endpoints for Hyperliquid HyperEVM. Additionally, we offer a custom gRPC streaming interface for Layer 1 data including real-time order book updates, fills, and market events—ideal for trading applications and monitoring.

Hyperliquid's architecture differs from traditional EVM chains. Dwellir provides access to HyperEVM state and L1 trading data. For specific historical data requirements, contact our team about dedicated node configurations optimized for your use case.

1. Sign up at dwellir.com and contact our team for Hyperliquid endpoint access. 2. Replace your current HyperEVM RPC URL (e.g., https://rpc.hyperliquid.xyz/evm) with your Dwellir endpoint. 3. For L1 data, use Dwellir's gRPC streaming interface. The HyperEVM API is fully compatible with standard Ethereum JSON-RPC methods.

Hyperliquid HyperEVM uses Chain ID 999 with HYPE as the native gas token. The network features sub-second finality via HyperBFT consensus and supports up to 200,000 orders per second. HyperEVM uses the Cancun hardfork with EIP-1559 enabled (priority fees are burned). The L1 and HyperEVM share state and consensus for seamless trading integration.

For HyperEVM, use standard EVM tooling including Web3.js, ethers.js, viem, and Web3.py. For L1 trading functionality, use the Hyperliquid Python SDK or gRPC clients. Development frameworks like Hardhat and Foundry work for HyperEVM smart contracts.

HYPE is fungible across Hyperliquid's L1 (HyperCore) and HyperEVM: 1) L1 to HyperEVM: Send HYPE to the system address 0x2222222222222222222222222222222222222222—it arrives as native gas on HyperEVM, 2) HyperEVM to L1: Send HYPE back to the same 0x222... address, and it's credited to your L1 account based on event logs. No separate bridge contract or wrapped token needed. This unified design means spot transfers between L1 trading and EVM smart contracts happen instantly within the same consensus. For other assets, use the official Hyperliquid bridge or third-party bridges like Across.

Hyperliquid has two execution environments sharing state: 1) HyperCore (L1): Purpose-built for trading—handles order books, perpetuals, spot markets via signed actions (not EVM transactions). Use for high-frequency trading, market making, and accessing native trading APIs, 2) HyperEVM: Standard EVM for Solidity smart contracts—use for DeFi protocols, NFTs, and general dApp development. Key insight: Both share consensus and state, so HyperEVM contracts can read L1 market data and HYPE moves freely between them. For trading bots, HyperCore's direct API is faster; for composable DeFi, HyperEVM integrates with standard EVM tooling.