Published May 15, 2026Documentation Index
Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
The GoldRush Hyperliquid WebSocket API now exposes a GoldRush-exclusive l4Book channel at wss://hypercore.goldrushdata.com/ws — an order-level view of the Hyperliquid book with no equivalent on the public Hyperliquid feed. A new recipe page shows how to maintain local book state, attribute flow by wallet, and reconstruct aggregated views from per-order detail.
Why it’s different from l2Book
- Per-order visibility - every entry is an individual order keyed by
oid, carryinguser,cloid,tif,orderType, and trigger metadata.l2Bookonly exposes{px, sz, n}aggregated per price level. - Snapshot then per-block diffs - one full
Snapshotof every resting order on subscribe, thenUpdatesmessages each block carryingorder_statuses(lifecycle events) andbook_diffs(per-order changes). Apply diffs against a localMap<oid, Order>. - GoldRush-native - not exposed on
wss://api.hyperliquid.xyz/ws. Theuserattribution and per-order metadata are surfaced only on the GoldRush endpoint.
What you can build
The recipe walks through patterns end-to-end with TypeScript and Python code:- Track individual orders by
oid- use the Hyperliquid order id as the primary key in local state; index oncloidto correlate fills back to a specific bot’s instructions. - Per-user flow attribution - group resting size by
userto surface market-maker behavior, spot spoofing patterns, or build per-trader heatmaps. Pair withclearinghouseStatefor position and margin context. - Reconstruct aggregated price levels - sum
szacross orders sharing alimitPxon the samesideto produce anl2Book-style view from L4 data. - Reconnect handling - drop local state and re-seed from the next
Snapshot; the snapshot is authoritative and supersedes anything held before the disconnect.