← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · ORDER-BOOK DELTAS

Crypto Order-Book Deltas: Null vs Zero - Handle Missing Fields Correctly

In a depth diff stream, a quantity of zero is an instruction, not a measurement. Missing update IDs mean the local book is no longer trustworthy.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

Binance's diff book depth stream sends updates with first and final update IDs and changed levels. A level with quantity "0" means remove that price level — not 'zero liquidity measured'. If update IDs don't chain (an event's previous final ID doesn't match the last processed one), updates were missed and the local book must be rebuilt from a fresh snapshot. Binance publishes a step-by-step procedure for managing a local order book this way.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
Level quantity "0"—Remove the level
Update ID chain breakMissed updates: resync—
Level not in updateUnchanged—
Snapshot lastUpdateIdStarting point—
Event timeOrdering only—
Order-Book Deltas: how to read each fieldOrder-Book Deltas: how to read each field: Level quantity "0" — Remove the level; Update ID chain break — Missed updates: resync; Level not in update — Unchanged; Snapshot lastUpdateId — Starting point; Event time — Ordering only.Level quantity "0"Remove the levelUpdate ID chain breakMissed updates: resyncLevel not in updateUnchangedSnapshot lastUpdateIdStarting pointEvent timeOrdering only
Order-Book Deltas: missing vs zero, field by field. Original ChartsPod editorial graphic.

Compare Crypto Order-Book Deltas across Binance, Bybit, OKX and Hyperliquid markets.

Open markets in ChartsPod

Handling policy

Policy for this sourcePolicy for this source: Apply zero as delete; Check ID continuity on every event; Resync from snapshot on breaks; Buffer events while syncing; Log resync count.POLICY FOR THIS SOURCEApply zero as deleteCheck ID continuity on every eventResync from snapshot on breaksBuffer events while syncingLog resync count
Apply this policy to every order-book deltas request. Original ChartsPod editorial graphic.

Illustrative: a heatmap shows a persistent bid wall that no one else sees. The client missed an update that set that level to 0, so it never deleted the level.

Conclusion

Related: Crypto Order-Book Snapshots: Null vs Zero - Handle Missing Fields Correctly, Spoofing-Like Order-Book Changes in Crypto: What Price Response Adds to the Reading.

Binance publishes a step-by-step procedure for managing a local order book this way.

Check Crypto Order-Book Deltas against a live market before relying on it.

Try it in ChartsPod

Questions readers ask

What does quantity 0 mean in a depth update?

Remove the price level.

What if update IDs don't chain?

Rebuild from a fresh snapshot.

Is a level absent from an update removed?

No; it's unchanged.

Sources and methodology

Field definitions come from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's Spot API documentation, read 17 October 2026. Where a schema was not visible in the documentation, this guide says so and describes defensive handling rather than asserting field behaviour.

  1. Binance USD-M: Diff. book depth streams — update IDs; quantity 0 removes a level.
  2. Binance USD-M: How to manage a local order book correctly — snapshot plus diff synchronisation.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.