Hyperliquid Data: Index HyperCore and HyperEVM

Index Hyperliquid's HyperCore orderbooks and HyperEVM contracts in one pipeline, decoded and delivered to your own database. Real-time and complete historical data, no node to run.

Hyperliquid is one of the fastest-growing onchain perpetuals venues, and its data lives in two places. HyperCore runs the perp and spot orderbooks fully onchain, where every order, cancel, trade, and liquidation settles at one-block finality under HyperBFT consensus. HyperEVM is a general EVM secured by that same consensus, where contracts, tokens, and DeFi apps run.

Indexing both layers is the hard part. Indexing Co covers HyperCore and HyperEVM in a single pipeline, decodes the data into the shape you want, and delivers it to your own PostgreSQL, warehouse, or webhook. Real-time and full history, with no node to operate.

Source HyperCore + HyperEVM

Ingest blocks and orderbooks

Decode raw to structured

Transform your TypeScript

Deliver your database

Why Hyperliquid data is hard

Two Layers, One App HyperCore orderbook activity and HyperEVM contract events are separate data sources. Most providers cover one, not both, so you end up stitching two systems together.

Raw Block Data, DIY The official HyperEVM archive is raw blocks in a requester-pays S3 bucket, stored as MessagePack compressed with LZ4 and keyed by block number. Turning that into decoded, queryable data means running a node or building an S3 ingestion pipeline yourself.

Orderbook Throughput HyperCore emits a high rate of order, fill, and liquidation events. Capturing that in real time without falling behind the chain head is its own engineering problem.

History That Is Actually Complete Backfilling a fast-moving venue means merging local node data with the S3 archive and handling the gaps. A clean, gap-free history is non-trivial to assemble.

What Indexing Co delivers for Hyperliquid

The DIY Path

Stand up and maintain the whole stack yourself.

Run a non-validating HyperEVM node, or ingest the requester-pays S3 bucket.
Decode MessagePack / LZ4 block data.
Capture HyperCore orderbook events separately.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

One pipeline covers both layers, delivered to your store.

HyperCore and HyperEVM in a single pipeline.
Decoded data, shaped by your TypeScript transform.
Lands in your PostgreSQL, BigQuery, warehouse, or webhook.
Real-time delivery plus complete backfilled history. No node, no S3 plumbing.

What you can index

HyperCore	HyperEVM
Orderbook, fills, and trades	Contract events and logs
Liquidations and funding	Token transfers (ERC-20, ERC-721)
Open interest and market state	Decoded transactions and traces
Spot markets	DeFi protocol state

A transform, not a subgraph

You write the indexing logic in TypeScript, not AssemblyScript, and change it without re-indexing from block zero. The example below shapes a decoded HyperEVM swap event into a row for your database.

// Illustrative: shape a decoded HyperEVM swap event into an output row
export function onSwap(event: DecodedEvent): SwapRow {
  return {
    block: event.blockNumber,
    timestamp: event.blockTimestamp,
    pool: event.address,
    trader: event.args.sender,
    amountIn: event.args.amountIn,
    amountOut: event.args.amountOut,
  };
}

Hyperliquid with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate HyperEVM nodes, S3 ingestion, and HyperCore capture.

Use Indexing Co if

You want HyperCore and HyperEVM decoded and delivered to your own database, with real-time plus complete history and no infrastructure to run.

FAQ

Does Indexing Co index HyperCore or just HyperEVM?

Both. HyperCore orderbooks, fills, and liquidations and HyperEVM contract events are indexed in the same pipeline and delivered to your destination.

Do I need to run a Hyperliquid node?

No. Indexing Co handles sourcing from HyperCore and HyperEVM, including the historical archive, so you do not run a node or ingest the raw S3 bucket.

Can I get complete historical Hyperliquid data?

Yes. We backfill history and merge it with real-time data so your dataset is gap-free from your chosen start block.

Where does the Hyperliquid data go?

Into your own destination: PostgreSQL, BigQuery, a warehouse, or a webhook. You define the output schema and own the storage.

How fast is the data?

Real-time delivery on dedicated infrastructure, plus historical backfill measured in hours rather than days.

Get Started

Index Hyperliquid in minutes. Set up your first HyperCore or HyperEVM pipeline without running a node.

Get a Demo | Open the Console