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.

301326 of 326 coins · most data · spot

2026-02-132026-09-1091 days~51 kB/day · 5 MB on diskspot
2025-07-022026-09-0290 days~51 kB/day · 4 MB on diskspot
2025-09-132026-09-0898 days~43 kB/day · 4 MB on diskspot
2025-10-242026-09-0574 days~51 kB/day · 4 MB on diskspot
2026-04-152026-09-1062 days~58 kB/day · 4 MB on diskspot
2025-10-272026-09-1064 days~54 kB/day · 3 MB on diskspot
2026-07-142026-09-1051 days~61 kB/day · 3 MB on diskspot
2025-10-092026-09-0160 days~45 kB/day · 3 MB on diskspot
2025-08-302026-08-2454 days~50 kB/day · 3 MB on diskspot
2025-10-312026-09-1050 days~49 kB/day · 2 MB on diskspot
2025-08-062026-07-0157 days~43 kB/day · 2 MB on diskspot
2025-12-152026-07-0154 days~43 kB/day · 2 MB on diskspot
2025-07-262026-08-0253 days~44 kB/day · 2 MB on diskspot
2025-12-022026-09-0848 days~44 kB/day · 2 MB on diskspot
2025-07-072026-07-2149 days~43 kB/day · 2 MB on diskspot
2025-08-252026-08-3142 days~43 kB/day · 2 MB on diskspot
2026-03-262026-08-2639 days~43 kB/day · 2 MB on diskspot
2026-02-212026-07-0127 days~58 kB/day · 2 MB on diskspot
2026-04-022026-09-0922 days~43 kB/day · 939 kB on diskspot
2026-04-152026-07-2317 days~43 kB/day · 726 kB on diskspot
2026-08-062026-09-0912 days~44 kB/day · 532 kB on diskspot
2026-08-062026-09-0912 days~43 kB/day · 522 kB on diskspot
2026-07-292026-09-098 days~43 kB/day · 341 kB on diskspot
2026-01-182026-09-088 days~43 kB/day · 340 kB on diskspot
2026-08-082026-09-097 days~43 kB/day · 301 kB on diskspot
2026-07-292026-09-097 days~43 kB/day · 298 kB on diskspot
← prevpage 7 of 7

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.