Hyperliquid via Dwellir

Hyperliquid is a purpose-built L1 blockchain optimized for trading. Dwellir runs its own Hyperliquid nodes and offers infrastructure beyond standard RPC: a custom gRPC gateway for Hypercore data, a real-time order book server, and a filtering Info API proxy — with edge servers in Singapore and Tokyo.

How Hyperliquid Works

Hyperliquid has two layers:

HyperCore — The native trading layer. Fully on-chain perpetual futures and spot order books. Every order, cancellation, trade, and liquidation settles within one block. Handles ~200,000 orders/second with sub-second finality via HyperBFT consensus.

HyperEVM — A general-purpose EVM smart contract layer that runs alongside HyperCore. Developers can deploy Solidity contracts that interact with HyperCore's liquidity. Chain ID: 999. Native gas token: HYPE.

Key properties:

All order books are fully on-chain — no off-chain matching
Sub-second block times with one-block finality
Perpetuals support up to 40x leverage (BTC); most assets 3–10x
Native spot trading with HIP-3 DEX deployment

What Dwellir Provides

Dwellir runs full Hyperliquid infrastructure: the official HL node, plus custom software built by Dwellir and the community for serving specific data channels.

For current pricing, features, and service details, see Dwellir Hyperliquid docs and Pricing.

Endpoint	What It Serves	Protocol	Reference
HyperEVM JSON-RPC	EVM state, smart contracts, blocks	HTTPS + WSS	hyperevm-json-rpc.md
Info API proxy	Market data, user state, metadata	HTTPS (POST)	info-api.md
L1 gRPC Gateway	Hypercore block/fill/orderbook streaming	gRPC	grpc-gateway.md
Orderbook WebSocket	Real-time L2/L4 order book data	WSS only	orderbook-websocket.md
Dedicated Node	Full stack, uncapped throughput	All	See below

What Dwellir Does NOT Proxy

Exchange API — Order placement, cancellation, transfers, and other write operations require EIP-712 signatures and go directly to api.hyperliquid.xyz/exchange. See native-api.md.

Native WebSocket — Hyperliquid's subscription WebSocket (wss://api.hyperliquid.xyz/ws) for user events, trades, and candles is separate from Dwellir's Orderbook WebSocket. See native-api.md.

Read vs Write Architecture

┌─────────────────────────────────────────────────────────┐
│  Your Application                                        │
├──────────────────┬──────────────────────────────────────┤
│  READ (Dwellir)  │  WRITE (Hyperliquid native)          │
│                  │                                       │
│  EVM state ──────┤  Place orders ─── api.hyperliquid.xyz │
│  Info queries ───┤  Cancel orders    /exchange           │
│  gRPC streams ───┤  Transfers        (requires sig)      │
│  Order book ─────┤  Set leverage                         │
└──────────────────┴──────────────────────────────────────┘

When to Use Which Reference

You want to...	Use this reference
Deploy or interact with Solidity contracts on HyperEVM	hyperevm-json-rpc.md
Query EVM state (balances, logs, blocks)	hyperevm-json-rpc.md
Get market data (prices, order books, candles, funding rates)	info-api.md
Query user positions, orders, fills, or balances	info-api.md
Get perpetuals/spot metadata (universe, leverage, assets)	info-api.md
Stream real-time order book updates with deep levels	orderbook-websocket.md
Build market-making or arbitrage systems	orderbook-websocket.md
Stream L1 block data or fill executions	grpc-gateway.md
Build indexers or data pipelines from Hypercore	grpc-gateway.md
Place, cancel, or modify orders	native-api.md
Subscribe to user events, trades, or candle updates	native-api.md
Access historical trade/fill data	historical-data.md

Dedicated Nodes

Full Hyperliquid stack on single-tenant infrastructure. No shared rate limits, uncapped throughput. Available in Tokyo (mainnet) and testnet configurations.

A dedicated node includes all Dwellir services (EVM JSON-RPC, Info API, gRPC Gateway, Orderbook Server) on isolated infrastructure.

For current pricing and configuration options, see Dwellir Hyperliquid Pricing.

Contact sales or subscribe via dashboard.dwellir.com.

Best Practices

Use Dwellir for reads, Hyperliquid native for writes — Dwellir provides the data infrastructure; order placement requires signatures and goes through api.hyperliquid.xyz/exchange.
Use the gRPC gateway for latency-sensitive streaming — the gRPC endpoint reads from disk and has lower latency than HTTP polling the Info API.
Use Dwellir's Orderbook WebSocket for book data — it's optimized for order book delivery with edge servers in Singapore and Tokyo.
Batch Info API queries — fetch combined endpoints like metaAndAssetCtxs (via public API) rather than per-asset queries. Check Info API docs for which types are available on the Dwellir proxy vs public endpoint.
Cache metadata — meta, spotMeta, and perpDexs are semi-static. Cache for 1-5 minutes.
Use l2Book via Info API for snapshots, Orderbook WS for streaming — the Info API gives point-in-time snapshots; the Orderbook WebSocket gives continuous updates.

Documentation Links

Dwellir Hyperliquid docs: dwellir.com/docs/hyperliquid
Dwellir L1 gRPC Gateway: contact support@dwellir.com for source access
Dwellir Orderbook Server: contact support@dwellir.com for source access
Dwellir REST Server: contact support@dwellir.com for source access
Hyperliquid API docs: hyperliquid.gitbook.io
Hyperliquid Python SDK: github.com/hyperliquid-dex/hyperliquid-python-sdk
Dwellir dashboard: dashboard.dwellir.com
Dwellir support: support@dwellir.com