anyone have a way to get full order history? >2000?
anyone have a way to get full order history? >2000?
2026-06-26 · Hyperliquid · 3 条相关讨论
anyone have a way to get full order history? >2000?
anyone have a way to get full order history? >2000?
You would have to download the replica_cmds from s3 historical archive
You would have to download the replica_cmds from s3 historical archive
**Gaps in the public hl-mainnet-node-data archive — fills missing after node restarts** Hi HL team — flagging a data-quality issue in the public historical archive (the hl-mainnet-node-data bucket: node_fills / fills_by_block and replica_cmds). There are systematic gaps where fills are missing from the published data itself, not my pipeline — the trades clearly happened on-chain. Pattern: when the archival node restarts, it resumes at the live chain tip without backfilling the blocks it missed. So there's a short window (minutes) with no exported fills, even though the chain kept producing blocks. Both node_fills/fills_by_block AND replica_cmds share the identical gap (same node), so it can't be recovered from either — only from a full archival node / the live API (limited retention). Example (UTC): on 2025-06-21, node_fills has no fills between 09:17:07 and 09:31:14 (~846s); the order id advanced ~439,000 across the gap, so the chain was live. In replica_cmds the pre-restart session ends with a truncated 31 MB stub (file 636550000.lz4, last block 09:17:07) and the next session resumes at 636553440.lz4 (09:31:14) — blocks ~636551021–636553439 are in no session. Same pattern on 2025-06-28 (03:38:56–03:43:58) and 2025-09-27 (block gap 744216993 to 744217001). These recur ~weekly, clustered 07–11 UTC. Questions: is this a known export limitation? Could the affected block ranges be re-exported / backfilled from a full archival node? If not, is there a recommended source for these historical fills? Happy to share the full list of windows. Thanks!
**Gaps in the public hl-mainnet-node-data archive — fills missing after node restarts** Hi HL team — flagging a data-quality issue in the public historical archive (the hl-mainnet-node-data bucket: node_fills / fills_by_block and replica_cmds). There are systematic gaps where fills are missing from the published data itself, not my pipeline — the trades clearly happened on-chain. Pattern: when the archival node restarts, it resumes at the live chain tip without backfilling the blocks it missed. So there's a short window (minutes) with no exported fills, even though the chain kept producing blocks. Both node_fills/fills_by_block AND replica_cmds share the identical gap (same node), so it can't be recovered from either — only from a full archival node / the live API (limited retention). Example (UTC): on 2025-06-21, node_fills has no fills between 09:17:07 and 09:31:14 (~846s); the order id advanced ~439,000 across the gap, so the chain was live. In replica_cmds the pre-restart session ends with a truncated 31 MB stub (file 636550000.lz4, last block 09:17:07) and the next session resumes at 636553440.lz4 (09:31:14) — blocks ~636551021–636553439 are in no session. Same pattern on 2025-06-28 (03:38:56–03:43:58) and 2025-09-27 (block gap 744216993 to 744217001). These recur ~weekly, clustered 07–11 UTC. Questions: is this a known export limitation? Could the affected block ranges be re-exported / backfilled from a full archival node? If not, is there a recommended source for these historical fills? Happy to share the full list of windows. Thanks!