Historical Orderbook Data: Check Provenance and Gaps

Historical orderbook data: Require capture timestamps, sequence rules and documented gaps before using an archive for fill research.

Historical orderbooks need a provenance audit before they support execution research. A downloadable archive may contain useful observations, but its existence does not establish complete history, licensed reuse, accurate timestamps, or a valid reconstruction of the book. Treat each of those as a separate evidence requirement.

The Reddit discussion promoted a historical orderbook archive. Provider availability, licensing, and completeness were not verified; some replies remained inaccessible. This article recommends no provider. Its acceptance contract is an original offline research exercise.

Historical orderbook data: write the data contract

Request venue and instrument identity, capture period, depth level, price and quantity units, timestamp meanings, update cadence, and schema version. Distinguish exchange event time, receipt time, archive creation time, and the time a file became available to your research system. A late-published historical record cannot be assumed available for an earlier decision.

IETF RFC 3339 standardizes timestamp representation. It does not verify a collector's clock or identify which event the timestamp describes. Preserve the provider's raw field and the normalization rule. Record clock uncertainty and unknown offsets rather than guessing them from apparent ordering.

Reconstruct snapshots and deltas deliberately

A snapshot represents a state; a delta changes that state. Confirm whether a delta quantity is a replacement or an increment and how deletion is represented. Check sequence identifiers, duplicates, reconnect boundaries, and the documented resynchronization rule. Coinbase's official feed guide distinguishes channel types. Its contracts illustrate why another venue needs its own specification.

Do not mix those venue rules by analogy. An archive built from periodic snapshots has different information from a complete ordered event stream. If a sequence gap cannot be repaired, mark the affected interval unavailable for the relevant analysis instead of carrying forward a seemingly valid book indefinitely.

A synthetic gap fixture

Create an invented snapshot with ten units at $50.00 and five at $50.10. Define replacement deltas that set the first level to six, then remove it. After those two events, only five units at $50.10 remain. Duplicate the removal event and confirm it does not create a negative quantity.

Now omit an intervening required sequence number. The reconstruction should enter an uncertain state until a valid resynchronizing snapshot arrives. This tests the declared contract. It does not establish that a real archive uses replacement semantics or contains repair snapshots; those details require provider evidence.

Keep fills and licensing separate

Even a correctly reconstructed observed book does not show the market after your hypothetical order was added. State arrival, priority, quantity, and market-response assumptions when building scenarios. Record missing-depth limitations beside outcomes. A historical-data pass is not proof of exact counterfactual fills.

Verify permitted research, commercial use, retention, and redistribution against current official terms. An announcement promising future coverage is not evidence that the coverage exists. Use Tradewink Advisory Research to locate offline input requirements. First complete the provenance checklist and run the gap fixture on fabricated records. Integrate an archive only after its contract and rights are independently supported; this article does not certify the promoted service.

Continue the research

Missed Trading Alerts: Reconcile the Exit Event Chain and Closing Equity Drawdown: A Reproducible Intraday Example develop adjacent checks. Use a small synthetic fixture first; these educational diagnostics do not validate a trading edge or change account settings.