Who Is Trading on HIP-3? The Data Stack Behind Arrakis's 175,703-Wallet Map
Arrakis published a HIP-3 participant map large enough to make the historical data layer visible: seven markets, 175,703 wallets, and 808M order events.
Back to Resources
Browse all Resources
Market Data Guides
Practical explanations for reading, testing, and using Hyperliquid and Lighter market data.
From HIP-3 Order Flow to a Defensible Wallet Taxonomy
A rerun test for HIP-3 wallet taxonomies: pull the same window twice, and confirm the buckets hold.
When HIP-3 Research Outgrows the Venue API
Venue APIs are excellent for narrow checks. The gap opens when the same HIP-3 reconstruction keeps getting rebuilt for a larger study.
HIP-3 historical data at L4: every order, cancel, and fill
0xArchive reconstructs every HIP-3 market to L4. Every order, cancel, and fill, attributed per trade, across 180+ builder-perp markets on Hyperliquid.
Hyperliquid Liquidation Data: What the Candle Hides
OHLCV shows the wick. Liquidation data shows the forced flow that caused it. How to read Hyperliquid liquidations and pull them from 0xArchive.
HIP-4 Outcome Market Data: The Price Is a Probability
On Hyperliquid's HIP-4 prediction markets the order-book price is an implied probability, not USD. How to read it, analyze it, and pull it from 0xArchive.
Lighter L3 Order-Level Data: Every Order, and Who Placed It
Lighter L3 is the full resting book, one row per order, with the wallet attached. Reconstruct queue position, attribute flow, and backtest with fills that reproduce.
Hyperliquid Order Book Data: L2 Levels and Full L4 Reconstruction
Hyperliquid order book data: full-depth L2 with order counts, L4 order-level depth with wallet attribution, and trade history back to April 2023.
When Checkpoint History Is Enough and When You Need Order-Level Depth
A question-first framework for deciding when checkpoint history is enough, when full L4 and order-level routes matter, and how to test the threshold on one Hyperliquid event window.
When Agent Workflows Need Replayable Market Data, Not Just Raw API Access
Why repeated Hyperliquid agent workflows benefit from typed tools, replayable history, and coverage-aware reruns once raw API pulls stop being enough.
How to Run a One-Symbol Parity Test Before You Migrate Historical Data
A practical Hyperliquid evaluator playbook for comparing native venue pulls against managed history with one symbol, one window, and one rerunnable study.
Hyperliquid Historical Data API for Backtesting: Native API vs 0xArchive
A proof-first guide to when Hyperliquid native is enough, when rerunnable backtests start acting like infrastructure, and how to test replayable managed history with one-symbol parity.
Funding Rate Arbitrage: Hyperliquid x Lighter
Compare BTC funding rates across Hyperliquid and Lighter with an open-source notebook that normalizes rates and detects arbitrage windows.
Example: BTC Liquidation Heatmap
Use an open-source notebook to visualize BTC liquidation events on Hyperliquid, including cascades and long-short imbalance analysis.