Skip to main content
Every order, trade, and fill on Hyperliquid and Lighter, live and historical, from one API. GoldRush serves HyperEVM on-chain transaction data, balances, and contract activity. For venue market data, the order book, trades, and order flow across both venues, you call 0xArchive. One key returns order books, trades, candles, funding, open interest, liquidations, and full order-level (L4) depth as normalized JSON, live or historical, across Hyperliquid and Lighter. The live API surface is a 0xArchive route, and so is every dated window behind it. No collectors, no backfill, no second pipeline for the second venue.

​
What One Key Returns

Market-data jobGoldRush0xArchive
HyperEVM on-chain and contract dataOn-chain transaction breadthNot the product job
Order books (L2), live and historical---20-level snapshots about every 1.2 seconds since April 2023, 24.6B+ records, 176 Hyperliquid symbols
Live API surface and replay---WebSocket subscriptions and exact-window replay on one socket
Order lifecycle and L4 routes---Every order add, fill, cancel, and TP/SL on Hyperliquid, with wallet attribution, since March 2026
Trades, funding, open interest, liquidations---Trades since April 2023, funding and open interest since May 2023, liquidations since December 2025
Multi-venue scope---Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter, each route family with stated start dates
Lighter coverage---Trades and funding since August 2025, L2 tick since January 2026, L3 order-level since March 2026
Coverage, freshness, gap context---Coverage, freshness, incidents, latency, and gaps on the same routes

​
Why Teams Choose 0xArchive

One key spans both venues with stated start dates: Hyperliquid order books and trades since April 2023, more than 24 billion records, plus HIP-3, HIP-4, and Spot families, and full order-level (L4) depth and lifecycle with wallet attribution since March 2026. Lighter trades and funding go back to August 2025, with L2 tick since January 2026 and L3 order-level since March 2026. Live WebSocket subscriptions and exact-window replay run on the same socket, and every response carries a request ID and a data-quality path you can check before a backtest trusts the window. Two venues, one API key, one schema, no separate pipeline for each. Every order, trade, and fill. One API.

​
Next Step

Open Best Hyperliquid Data API or Lighter Historical Data API, test one route, then compare plans.
Last modified on June 28, 2026