All chains
Hyperliquid

Hyperliquid

Other App Chain / Chain ID 999

Hyperliquid is a high-performance Layer 1 blockchain optimized for onchain perpetual trading with instant finality.

Quick Facts
Networks 4
Runtime Other
Chain ID 999
Real-time Yes
Data tables 2
Category App Chain
Networks
4
Data tables
2
Chain ID
999
Coverage
Real-time + archive
Start block
0 (genesis)
License
Open-source SDK

Networks

hyperliquid-fills
Real-time Other mainnet 2 tables
hyperliquid-mainnet
Real-time EVM mainnet 5 tables
hyperliquid-replica-cmds
Other mainnet 2 tables
hyperliquid-testnet
EVM testnet 3 tables

Hyperliquid on SQD

Validated at ingestion

Hyperliquid data is validated by SQD Network workers before it reaches the Portal. Validation is performed across the network rather than by a single ingestion node, so a faulty upstream source can't poison the dataset.

Decoded, schema-typed

2 Hyperliquid tables (blocks & fills), decoded and schema-typed, ready to query. Your indexer queries the data directly.

Archive plus real-time

Single Portal endpoint serves Hyperliquid from genesis through the current head, with sub-second hot-path latency. No separate streaming pipeline to wire up.

Open-source SDK

The Pipes SDK is open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your Hyperliquid pipeline on your own infrastructure pointing at the SQD Portal.

Build with Hyperliquid data

Common production patterns teams build with SQD on Hyperliquid.

Available Data

blocks

Block headers with timestamps, gas usage, miner info, and consensus data.

fills

Fills data for Hyperliquid.

Stream Hyperliquid data in two lines

Example below uses the public Hyperliquid endpoint, no API key required for development. For full SDK reference, see the documentation.

1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/hyperliquid-fills/stream' \
3 -H 'Content-Type: application/json' \
4 -d '{
5 "type": "evm",
6 "fromBlock": 0,
7 "toBlock": 100,
8 "fields": {
9 "block": {"number":true,"timestamp":true},
10 "transaction": {
11 "hash": true,
12 "from": true,
13 "to": true,
14 "value": true
15 }
16 },
17 "transactions": [{}]
18 }'
hyperliquid-fills/stream
EVM · blocks 0100

Frequently asked questions

How does SQD compare to pulling Hyperliquid data from its own API?
Pulling Hyperliquid data from its native API means polling, handling rate limits, persisting raw responses, and managing reorgs or replays yourself. SQD pre-indexes Hyperliquid into decoded, schema-typed tables (blocks & fills) served as a single streaming endpoint, with full historical depth and the same access pattern you would use for any other chain on SQD.
What does SQD cost for Hyperliquid data?
The public Portal endpoint at portal.sqd.dev/datasets/hyperliquid-fills is free for development with no API key. Production workloads run on the SQD Portal with tiered pricing based on the network and request volume. See the pricing page for current tiers, or contact us for an enterprise quote.
Can I self-host SQD's Hyperliquid indexer?
Yes. The Pipes SDK is open-source. You can run a Hyperliquid pipeline on your own infrastructure pointing at the SQD Portal.
Can I export Hyperliquid data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Hyperliquid data from the Portal into Postgres, ClickHouse, MongoDB, SQLite, Parquet, or a custom target you implement. See the SDK docs for the connector reference.
Does SQD validate Hyperliquid data?
Hyperliquid data ingested into SQD is validated and signed by SQD Network workers before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream source can't poison the dataset.
Does SQD support real-time Hyperliquid data?
Yes. Hyperliquid is served with both real-time and historical data from the same Portal endpoint, with sub-second latency on the hot path. No separate streaming pipeline to wire up.

Start building with Hyperliquid

Access Hyperliquid data through the SQD Portal, free tier available.