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 supported 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. No collectors, no backfill, no second pipeline for the second venue.

​
What One Key Returns

​
Where GoldRush Fits

0xArchive reads market microstructure, not wallet state; decoded on-chain activity is the territory of GoldRush, by Covalent. Its site lists wallet portfolios and token balances across 100+ chains, decoded transaction activity feeds, OHLCV token pricing, real-time new-DEX-pair notifications, and custom pipelines that push decoded chain data into ClickHouse, Postgres, Kafka, or S3, with credit-based pricing, a 14 day free trial, and x402 pay-per-request live on Base Sepolia with mainnet listed as coming soon. Hyperliquid appears among its protocol-native schemas. When the question is what a wallet holds, what a contract did, or how to feed decoded chain data into a warehouse, that question is GoldRush’s to answer, and 0xArchive is not the right fit for it; this API holds the order books and trades those wallets moved through, not their balances. The split is on-chain state versus market microstructure: decoded transactions do not carry the resting order book, and a balances API cannot replay the book at a timestamp.

​
When To Use 0xArchive

One key spans both venues with stated start dates: Hyperliquid order books and trades since April 2023, plus HIP-3, HIP-4, and Spot families, and full order-level (L4) depth and lifecycle with wallet attribution since March 2026. Lighter trade history reaches back to January 2025 for supported markets and funding 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. Use one API for supported Hyperliquid and Lighter market-data routes, with coverage and freshness stated by family and window.

​
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 August 12, 2026