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.

150 of 844 coins · most data

2025-01-252026-09-10594 days~158 MB/day · 92 GB on diskperpetuals
2025-01-252026-09-10594 days~155 MB/day · 90 GB on diskperpetuals
2025-01-252026-09-10594 days~146 MB/day · 85 GB on diskperpetuals
2025-01-252026-09-10594 days~126 MB/day · 73 GB on diskperpetuals
2025-01-252026-09-10594 days~123 MB/day · 72 GB on diskperpetuals
2025-01-252026-09-10594 days~112 MB/day · 65 GB on diskperpetuals
2025-01-252026-09-10594 days~107 MB/day · 62 GB on diskspot
2025-01-252026-09-10594 days~95 MB/day · 55 GB on diskperpetuals
2025-01-252026-09-10594 days~93 MB/day · 54 GB on diskperpetuals
2025-01-252026-09-10594 days~93 MB/day · 54 GB on diskperpetuals
2025-01-252026-09-10594 days~92 MB/day · 53 GB on diskperpetuals
2025-01-252026-09-10594 days~88 MB/day · 51 GB on diskperpetuals
2025-01-252026-09-10594 days~88 MB/day · 51 GB on diskperpetuals
2025-01-252026-09-10594 days~86 MB/day · 50 GB on diskperpetuals
2025-01-252026-09-10594 days~84 MB/day · 49 GB on diskperpetuals
2025-01-252026-09-10594 days~82 MB/day · 48 GB on diskperpetuals
2025-01-252026-09-10594 days~81 MB/day · 47 GB on diskperpetuals
2025-01-252026-09-10594 days~79 MB/day · 46 GB on diskperpetuals
2025-01-252026-09-10594 days~79 MB/day · 46 GB on diskperpetuals
2025-01-252026-09-10594 days~79 MB/day · 46 GB on diskperpetuals
2025-01-252026-09-10594 days~77 MB/day · 45 GB on diskperpetuals
2025-01-282026-09-10589 days~77 MB/day · 45 GB on diskspot
2025-10-022026-09-10344 days~132 MB/day · 44 GB on diskperpetuals
2025-01-252026-09-10594 days~76 MB/day · 44 GB on diskperpetuals
2025-01-252026-09-10594 days~76 MB/day · 44 GB on diskperpetuals
2025-01-252026-09-10594 days~74 MB/day · 43 GB on diskperpetuals
2025-03-242026-09-10536 days~81 MB/day · 43 GB on diskspot
2025-01-252026-09-10594 days~73 MB/day · 42 GB on diskperpetuals
2025-01-252026-09-10594 days~72 MB/day · 42 GB on diskperpetuals
2025-01-252026-09-10594 days~72 MB/day · 42 GB on diskperpetuals
2025-01-252026-09-10594 days~72 MB/day · 42 GB on diskperpetuals
2025-01-252026-09-10594 days~71 MB/day · 41 GB on diskperpetuals
2025-01-252026-09-10594 days~70 MB/day · 41 GB on diskperpetuals
2025-01-252026-09-10594 days~70 MB/day · 40 GB on diskperpetuals
2025-04-112026-09-10512 days~80 MB/day · 40 GB on diskspot
2025-01-252026-09-10594 days~67 MB/day · 39 GB on diskperpetuals
2025-01-252026-09-10594 days~67 MB/day · 39 GB on diskperpetuals
2025-01-252026-09-10594 days~66 MB/day · 38 GB on diskperpetuals
2025-01-252026-09-10594 days~66 MB/day · 38 GB on diskperpetuals
2025-01-252026-09-10594 days~65 MB/day · 37 GB on diskperpetuals
2025-01-252026-09-10594 days~64 MB/day · 37 GB on diskperpetuals
2025-01-252026-09-10594 days~64 MB/day · 37 GB on diskperpetuals
2025-01-252026-09-10594 days~63 MB/day · 37 GB on diskperpetuals
2025-01-252026-09-10594 days~63 MB/day · 36 GB on diskperpetuals
2025-01-252026-09-10594 days~62 MB/day · 36 GB on diskperpetuals
2025-01-252026-09-10594 days~62 MB/day · 36 GB on diskperpetuals
2025-01-252026-09-10594 days~61 MB/day · 36 GB on diskperpetuals
2025-02-132026-09-10566 days~64 MB/day · 36 GB on diskperpetuals
2025-01-252026-09-10594 days~60 MB/day · 35 GB on diskperpetuals
2025-01-252026-09-10594 days~60 MB/day · 35 GB on diskperpetuals
page 1 of 17next →

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.