What One Key Returns
Why Teams Choose 0xArchive
Backtests break when historical data cannot be tied to venue semantics, timestamp windows, route families, and data-quality state. 0xArchive keeps those concerns together so a research result is reproducible. A Hyperliquid backtest starts with/v1/hyperliquid/orderbook/BTC/history for 20-level book snapshots since April 2023, adds /v1/hyperliquid/trades/BTC for the matching tape, pulls /v1/hyperliquid/funding/BTC for carry, and gates the window with a /v1/hyperliquid/freshness/BTC check before the model trusts it. For order-level book work, /v1/hyperliquid/orderbook/BTC/l4/history returns every resting order with oid and user_address since March 2026, the depth a DIY collector cannot rebuild after the fact. Use the separate order-history and order-flow routes for lifecycle records.
Store the request ID when the response exposes it, and check data quality before a backtest trusts the window. Store route, symbol, parameters, cursor chain, request IDs, and freshness result with the dataset and the pull is repeatable months later. Equities, dozens of centralized venues, order placement, account state, and wallet indexing are outside this job — Hyperliquid and Lighter are the whole surface.
Run One Route
Evaluation Questions
1
Choose the venue family
Start with Venue coverage. Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter each keep their own history; do not normalize them into one symbol namespace.
2
Choose the time primitive
Use REST history routes for bounded pulls with explicit UTC start and end. Use WebSocket replay when event order and timing are the requirement.
3
Gate the window
Check coverage, freshness, incidents, and latency through
/v1/hyperliquid/freshness/BTC and /v1/data-quality/incidents before writing training data, reports, alerts, or strategy results.