tickfoundry
capture livesign inget the data →

Hyperliquid. Pull any coin, any days.

A coin is one perp, spot pair or HIP-3 market, named the venue's way (BTC, @107, xyz:CL). Pick one, pick a range, get l1 / 25-level l2 / trades parquet — rebuilt from the chain's own order-event stream, one row per block, since 2025-01-25. Included with a plan bought for Hyperliquid; $50/mo on a Polymarket plan; one free sample day. Building this yourself — pulling the chain's order-event archive out of requester-pays S3 and replaying it into books — runs to around $10,000 in egress and compute.

Pull several coins in one bundle594 days 2025-01-252026-09-10 · gapless · 844 coins · 6.0 TB on disk
Coinsnone yet — use “+ pull with others” on the rows below, or search a symbol
Tables
Create a free account to download1 kB · 0 coins · 3 tables
A free account pulls 2026-08-12, any coins, up to 1.0 GB, at no cost; every other day needs a plan bought for Hyperliquid, or the add-on on a Polymarket plan — see plans.

201234 of 234 coins · most data · perpetuals

2025-01-252026-08-25430 days~8 MB/day · 3.5 GB on diskperpetuals
2025-01-252026-09-10501 days~7 MB/day · 3.3 GB on diskperpetuals
2025-01-252026-08-23533 days~6 MB/day · 3.2 GB on diskperpetuals
2025-01-252026-09-10594 days~5 MB/day · 2.9 GB on diskperpetuals
2025-01-252026-09-06379 days~8 MB/day · 2.8 GB on diskperpetuals
2025-01-252026-09-07530 days~5 MB/day · 2.7 GB on diskperpetuals
2025-01-252026-08-27453 days~6 MB/day · 2.7 GB on diskperpetuals
2025-01-252026-09-09511 days~5 MB/day · 2.6 GB on diskperpetuals
2025-01-252026-09-08487 days~5 MB/day · 2.6 GB on diskperpetuals
2025-01-252026-09-09397 days~7 MB/day · 2.6 GB on diskperpetuals
2025-08-212026-08-27356 days~7 MB/day · 2.4 GB on diskperpetuals
2025-01-252026-09-08515 days~4 MB/day · 2.0 GB on diskperpetuals
2025-01-252026-09-10502 days~4 MB/day · 1.9 GB on diskperpetuals
2025-01-252026-09-07511 days~3 MB/day · 1.7 GB on diskperpetuals
2025-10-082026-09-1053 days~30 MB/day · 1.6 GB on diskperpetuals
2025-10-292026-09-10121 days~11 MB/day · 1.3 GB on diskperpetuals
2025-01-252026-08-25449 days~3 MB/day · 1.1 GB on diskperpetuals
2025-01-252026-09-04331 days~2 MB/day · 724 MB on diskperpetuals
2026-01-122026-09-1035 days~10 MB/day · 335 MB on diskperpetuals
2025-01-252026-08-23267 days~769 kB/day · 201 MB on diskperpetuals
2025-01-252026-09-04298 days~83 kB/day · 24 MB on diskperpetuals
2025-01-252026-09-10533 days~42 kB/day · 22 MB on diskperpetuals
2025-01-252026-09-09407 days~42 kB/day · 17 MB on diskperpetuals
2025-01-262026-09-08407 days~42 kB/day · 17 MB on diskperpetuals
2025-01-252026-09-10401 days~42 kB/day · 17 MB on diskperpetuals
2025-01-252026-09-04345 days~42 kB/day · 14 MB on diskperpetuals
2025-01-252026-09-02325 days~42 kB/day · 13 MB on diskperpetuals
2025-01-292026-08-23306 days~42 kB/day · 13 MB on diskperpetuals
2025-01-252026-08-28270 days~42 kB/day · 11 MB on diskperpetuals
2025-01-252026-08-23257 days~42 kB/day · 11 MB on diskperpetuals
2025-01-252026-08-23249 days~42 kB/day · 10 MB on diskperpetuals
2025-01-292026-08-23228 days~42 kB/day · 9 MB on diskperpetuals
2025-01-292026-08-28218 days~42 kB/day · 9 MB on diskperpetuals
2025-01-252026-09-05216 days~42 kB/day · 9 MB on diskperpetuals
← prevpage 5 of 5

What is on disk

Top of book (every change)hl_l1

Best bid and ask with sizes and the spread, one row per block in which the top of book changed, replayed from the chain's own order events — not sampled from a websocket. No consecutive duplicates.

2025-01-252026-09-10 · 594 days · 393 GB · 258,509 files
Order book — 25 levels, every changehl_l2

The 25-level book on both sides — price, size and the number of resting orders at each level — one row per block in which any of it changed. Wide columns (bid_px_1 … ask_n_25), unused levels null. This is the table the venue's own websocket cannot give you: Hyperliquid pushes l2Book snapshots only, throttled to seconds.

2025-01-252026-09-10 · 594 days · 5.6 TB · 258,509 files
Trades (fills)hl_trades

Every fill the chain executed: price, size, taker side, order id, the taker's wallet, fee and fee token, closed PnL and start position, and the settlement transaction hash. From 2025-03-22 straight from the node's fills tape; before that synthesized from the taker's own fill status (see caveats).

2025-01-252026-09-10 · 593 days · 107 GB · 258,113 files
Read before you pull
  • One row per block, not per message. Blocks land about every 70 ms; l1 has a row for every block in which the top of book changed, l2 for every block in which any of the 25 levels changed, trades one row per fill. msg_seq is the block height.
  • A day is block-aligned, not midnight-aligned. Filter on ts_src_ms for strict UTC days.
  • The book is wide. bid_px_1 … ask_n_25 — price, size and resting-order count per level, best first, unused levels null. Full 25 levels on every plan.
  • Fills before 2025-03-22 are synthesized. No fills tape exists upstream before 2025-03-22, so taker fills in that era are derived from each taker order's own filled size and average price against the resting book (source_event_type = l3_taker_status). price, size, side, oid and user are set; transaction_hash, tid, dir, fee, fee_token, closed_pnl and start_position are null. Resting orders that expired or were cancelled without an event can linger in the book until the order-id-gap inference catches them.
  • Spot books start unseeded. The archive has no snapshot before its first day, so resting spot depth is thinner than steady state for the first day or two.
  • A 924-block hole on 2025-07-19. Heights 668379075 onward, roughly the last minutes of one source object: the object is truncated in Hyperliquid's own bucket. Every coin is affected for that interval; nothing else that day.
  • Every bundle ships a per-coin quality scorecard and a README with the schemas and these caveats for your exact range. Schema reference: /docs/hyperliquid.