Historical Data - Hyperliquid Market Archives

Dwellir preserves Hyperliquid node data in its source record formats and offers processed datasets for backtesting, research, and analysis. This page is the single inventory for S3 Bucket contents, formats, access, pricing, and product selection.

For sample design, manifests, timestamp semantics, TWAP joins, liquidations, account-state replay, and commercial use, see archive research and validation.

S3 bucket coverage

Inventory measured on 2026-10-01 UTC.

Compressed size and file count

The coverage table shows the compressed download size and file count for each available prefix. You can use these totals before buying archive access.

Sizes use decimal units: 1 GB is 1 billion bytes, and 1 TB is 1 trillion bytes. Decompressed files need additional storage.

Monthly averages use the last three calendar months with files on every date. Shorter histories use fewer months.

For a selected range, estimate volume as days / 30.5 × monthly average. Trading activity changes file sizes, so the result is approximate.

File count is the number of compressed files, not the number of blocks, events, or orders. File dates do not establish that every source record is present.

Archive formats

Native JSON and JSONL payloads are LZ4-compressed. Decompress .lz4 objects before parsing the record shape for their prefix. Generated order-book snapshots use <height>.json.lz4, while periodic ABCI state uses <height>.rmp.lz4. The latter contains RMP-encoded node state, not JSON.

Most current *_by_block feeds use an envelope with local_time, block_time, sequential block_number, and a feed-specific events array. The replica_cmds records contain abci_block and execution responses. Its abci_block.round is a consensus round, can skip, and must not be treated as the sequential block number.

The fills history spans 3 stored prefix generations:

Observed objects for these generations overlap, so their bounds are not mutually exclusive schema cutover dates. Select the parser from the object prefix and record shape. For processed analysis, tick data converts node_fills_by_block records into CSV or Parquet. For query access, use the Hyperliquid Index fills API.

Current field-level references are available for blocks, fills, order statuses, raw book diffs, misc events, and TWAP statuses.

Order-book reconstruction requires a known state seed, such as an orderbook_snapshots object generated from periodic ABCI state, followed by ordered node_raw_book_diffs_by_block records. Raw diffs alone cannot establish the starting book.

Choosing a historical product

To discover symbols before requesting data, use the Info endpoint. Perpetual names come from meta; spot names come from spotMeta.

Real-Time Data

For live market data, see:

• Order Book Server - Real-time L2/L4 order books and trades
• gRPC Streaming - StreamBlocks, StreamFills, and more

Pricing

API plan prices, included responses, and rate limits are on the pricing page. Current export credit prices are shown on the OHLCV Data tab.

Access

For OHLCV data: sign up at the dashboard and visit the OHLCV Data tab to buy export credits and generate CSV or Parquet files for any market at 1s, 1m, or 5m intervals.

For S3 Bucket archival data, tick data, and other historical products:

Email: support@dwellir.com

Include in your request:

• Prefix or data product needed
• Date range
• Preferred format
• Use case description

Use the coverage table and date-range estimator to plan downloads before purchase.

Frequently asked questions

How large are the archive files, and how many files will I receive?

The coverage table lists compressed size and file count per prefix. Use the date-range estimator for a shorter selection. Download volume varies with trading activity.

Which Hyperliquid historical data should I use for backtesting?

It depends on what your strategy trades on. Bar-based strategies can use OHLCV candles at 1s, 1m, or 5m. Execution backtests need fill-level tick data or the node_fills_by_block prefix. Order-level replay needs orderbook_snapshots plus node_raw_book_diffs_by_block. Their overlapping archive coverage starts on 2026-04-14.

How far back does Hyperliquid historical data go?

replica_cmds starts on 2025-01-25. Fills start on 2025-03-22 in the node_trades prefix, and node_fills_by_block plus OHLCV candles start on 2025-07-27. The full per-prefix table is in S3 bucket coverage.

How much does Hyperliquid historical data cost?

API plans start at $49/month, and 1 response = 1 API credit. OHLCV exports cost 1 export credit per market, interval, and format. S3 Bucket archive data and tick data are quoted per dataset. See Pricing.