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 is 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 is 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.

Dwellir CLI

The Dwellir CLI (dwellir) provides terminal access to endpoint discovery, API key management, usage monitoring, and documentation. Useful for quickly finding Hyperliquid endpoint URLs, reading docs without leaving the terminal, and managing keys in CI pipelines. See dwellir-cli.md.

# Install
curl -fsSL https://raw.githubusercontent.com/dwellir-public/cli/main/scripts/install.sh | sh

# Find all Hyperliquid endpoints
dwellir endpoints search hyperliquid

# Read Hyperliquid docs as markdown
dwellir docs search hyperliquid
dwellir docs get hyperliquid/info-endpoint

# Manage API keys and check usage
dwellir keys list
dwellir usage summary

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

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

1. Use Dwellir for reads, Hyperliquid native for writes. Dwellir provides the data infrastructure; order placement requires signatures and goes through api.hyperliquid.xyz/exchange.

2. Use the gRPC gateway for latency-sensitive streaming. The gRPC endpoint reads from disk and has lower latency than HTTP polling the Info API.

3. Use Dwellir's Orderbook WebSocket for book data. It's optimized for order book delivery with edge servers in Singapore and Tokyo.

4. 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.

5. Cache metadata. meta, spotMeta, and perpDexs are semi-static. Cache for 1-5 minutes.

6. 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