Skip to main content
GoldRush documents raw Hyperliquid and on-chain data workflows, including archival access. 0xArchive is the route-addressed market-data path for Hyperliquid and Lighter order books, trades, replay, and order-level depth. One key returns order books, trades, candles, funding, open interest, liquidations, Hyperliquid L4 order-level data and Lighter L3 individual-order depth as normalized JSON, live or historical. The live API surface is a 0xArchive route, and so is every dated window behind it. 0xArchive removes venue collection and historical backfill work; supported reconstruction routes return a checkpoint/snapshot. A snapshot-only consumer can use that state directly. A continuously updated local L4 book still must apply ordered diffs or replay, detect gaps, and reconstruct state after the checkpoint; the API does not remove those local-state obligations.
Evidence checked August 28, 2026. GoldRush’s Hyperliquid API overview documents managed Info and WebSocket access, including a live l4Book stream with per-order snapshots and per-block diffs containing fields such as user, oid, and cloid. The cited overview does not state Lighter coverage or a historical L4 window; compare its live L4 with 0xArchive’s Lighter L3 route. The 0xArchive route claims use Hyperliquid L4, Lighter L3, and Venue coverage.

​
What One Key Returns

​
Where GoldRush Fits

0xArchive reads market microstructure, while GoldRush’s Hyperliquid API overview documents managed Info and WebSocket access, including a live l4Book stream with per-order snapshots and per-block diffs containing fields such as user, oid, and cloid. The cited page does not state Lighter coverage or a historical L4 window. Choose GoldRush when managed Hyperliquid protocol access is the requirement; choose 0xArchive when the requirement is a bounded historical Hyperliquid or Lighter order-book route. If the job is protocol access rather than a market-data archive, 0xArchive is not the right fit for that layer. The split is on-chain state versus market microstructure. Decoded transactions and account state do not substitute for a route that returns the resting book at a requested time, and a live L4 stream does not by itself establish historical L4 retention.

​
When To Use 0xArchive

One key spans both top-level venue APIs with family-specific start dates: Hyperliquid core order books and trades since April 2023; HIP-3, HIP-4, and Spot are separate Hyperliquid families with their own routes and dates; Hyperliquid L4 begins in March 2026 on core and HIP-3; Spot order events and reconstructable checkpoints require separate coverage checks and in May 2026 on HIP-4, while lifecycle history is route-specific. The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. Funding and OI start in August 2025, L2 tick starts in January 2026, and L3 order-level depth starts in March 2026. Live subscriptions share the socket with timed replay on supported standard channels and checkpoint-anchored bulk replay for core L4. Spot, HIP-3, and HIP-4 L4 are real-time-only. Store the request ID when the response exposes it and check data quality before a backtest trusts the window. Two top-level venue APIs, one key, separate route families and schemas.

​
Next Step

Open Best Hyperliquid Data API or Lighter Historical Data API, test one route, check the per-family windows on Venue coverage, then compare plans.
Last modified on September 14, 2026