Most order book data people work with is L2 — aggregated size at each price level, no visibility into individual orders. L4 goes further: every individual order, tracked from placement to cancellation or fill, with its own identity through the book’s lifetime.
What L4 gives you that L2 can’t
With L2 you can see that there’s 40 BTC of bids at a price level. With L4 you can see that it’s composed of, say, 12 separate resting orders, when each was placed, and which ones get pulled the instant price approaches — a pattern L2 aggregation hides completely. This level of granularity is what real market microstructure research and serious execution algorithms are built on.
Why reconstruction is non-trivial
Hyperliquid’s raw stream gives you the primitives — order events, not a pre-built order-by-order book state. Reconstructing a correct, gap-free L4 book means tracking every add/modify/cancel/fill event in the right sequence, handling the stream’s actual event ordering correctly (see our post on HyperBFT consensus for why naive timestamp sort isn’t always safe), and reconciling against periodic snapshots to catch any drift.
Summary
L4 reconstruction unlocks a level of order book detail L2 snapshots simply don’t contain — but building it correctly means handling event ordering and stream reconciliation with real care, not just replaying events in the sequence they happened to arrive.