ReadNOW

Hyperliquid first reveals up as a worth story.

In a weak crypto tape, HYPE stored attracting consideration whereas the standard majors appeared heavier. That doesn’t show something in regards to the venue’s market construction. A token chart just isn’t an audit path; worth efficiency compresses flows, incentives, listings, buybacks, leverage, and narrative into one line.

However it does clarify why the venue is price opening.

The higher query just isn’t whether or not HYPE went up. It’s what sort of market object sits beneath that focus, and whether or not the general public ebook exposes sufficient state for an outsider to reconstruct the transferring floor of the market, reasonably than simply one other trade UI.

A pool snapshot and a ebook snapshot reply completely different questions, and this submit is about what occurs after the snapshot. A single l2Book pull is a measurement. An audit path is a sequence.

That distinction got here out of prior AMM work, the place the recurring blocker was less complicated: you can not motive ahead from a market state till the state object is outlined. If the article is unstable, over-abstracted, or blended in with hidden assumptions, a later monitor, rule engine, or studying loop dangers becoming artifacts as a substitute of mechanism. Hyperliquid turned the following take a look at case as a result of its public CLOB floor appeared archivable sufficient to strive.

The AMM facet has its personal model of this drawback. Bunni is a compact hook-side instance: its autopsy traced the failure to Bunni’s personal accounting logic, to not Uniswap v4’s core swap math. As soon as a pool provides customized protection logic on prime of the AMM, that logic turns into a part of the state machine an auditor has to comply with, and it wants sequence-level audit, not a single steadiness test.

Hyperliquid fingers the identical drawback a distinct object. There are not any pool reserves or hook accounting right here. The state is a transferring ebook: posted depth, trades, funding, open curiosity, mark-oracle premium, and reference mids pulled from different venues.

Hyperliquid begins from a distinct object

The static distinction is acquainted: callable stock versus posted depth.

An AMM pool can normally be inspected as a compact state object: reserves, liquidity vary, payment tier, swap logs, pool worth. A CLOB needs to be watched as a transferring floor as a substitute — ebook updates, trades, funding, open curiosity, mark-oracle context, and foundation towards reference mids. Cancels and reposts usually present up solely as depth that moved between snapshots, with no occasion marking the change.

On the AMM facet, the market object continues to be a pool: reserves, curve state, LP accounting, payment logic, and now hook state. Hooks and dynamic charges are an try and make that passive stock extra conditional, which is nearer to what a CLOB order already is by default — posted at a worth, for a measurement, till the maker cancels, till it fills, or till threat adjustments.

On the CLOB facet, the article is posted depth backed by lively makers, margin guidelines, funding, and a threat engine, not a pool defending passive stock. The seen stress indicators comply with from that: unfold, seen depth, signed move, funding, OI, mark-oracle premium, and foundation. Neither floor is being scored as safer right here; the article being inspected is simply completely different.

Hyperliquid paperwork the ebook as HyperCore / L1 state with price-time precedence matching. The general public information API and WebSocket path are the outsider observer path – twenty seen ranges per facet, callable from outdoors, which is what makes the ebook L1-settled, API-observable, and self-archivable within the first place. Archive the general public streams, normalize the rows, and label what by no means entered the artifact.

What the structure makes observable

This issues as a result of the general public stream just isn’t the identical factor as HyperCore itself. HyperCore contains the order books internally; what the API exposes is an observer path, not a byte-for-byte replay of that inside state.

Three layers fall out of that. Public feeds — l2Book, trades, metaAndAssetCtxs, exterior reference mids – are the primary. Derived metrics come second: unfold, seen depth, imbalance, signed move, funding/OI motion, mark-oracle premium, cross-venue foundation. The third layer stays hidden no matter how lengthy you acquire: maker intent, true queue precedence, non-public latency, account-level margin state, the complete liquidation path, risk-engine thresholds.

Reconstructing the transferring ebook

There isn’t any level reasoning ahead from a ebook state if the ebook state itself is barely a screenshot, so the primary process right here is reconstruction, not prediction.

The workflow is apparent: archive public streams, normalize them into book-timestamped rows, be part of nearest-prior perp context and reference mids, compute derived fields, and mark gaps as a substitute of filling them.

A neighborhood collector on BTC, ETH, and SOL pulls WebSocket l2Book and trades, periodic metaAndAssetCtxs, and Binance/Bybit perp mids as exterior anchors. Foundation here’s a reconciliation sign, not a mispricing verdict. The output is a partial outsider artifact – one row per ebook commentary with unfold, seen depth bands, sixty-second signed move, joined meta fields, cross-market foundation, and hole flags.

Any future monitor, rule engine, or agent that makes use of this knowledge inherits the identical observable boundary: it can’t act on maker intent or hidden margin state, as a result of these by no means entered the artifact to start with.

The figures under use a 7-day (168 h) assortment window (2026–07–13T00:00Z-2026–07–19T23:59Z; 112,626 BTC ebook rows) — the longest totally steady stretch in a roughly two-week assortment run, with no reference-feed or WS outages inside it. One joined row from the center of the run reveals how the fields line up: at 11:59:44 UTC on Jul 16, unfold 0.16 bps; seen 10 bps depth ~$10.6M; sixty-second signed move ~−$79k; funding joined from the nearest-prior meta ballot; HL mid inside a number of bps of Binance and Bybit mids.

This row doesn’t clarify maker intent, queue precedence, or liquidation causality. What it does present is narrower: the ebook, commerce tape, perp context, and reference mids be part of into one defensible outsider market-state artifact.

Liquidity, leverage, and pricing stress

The joined row above reads by means of 4 surfaces. Liquidity: sub-bps unfold with thick seen near-mid depth. Stress: heavy sell-side signed move, with the seen ebook leaning ask-heavy whereas takers hit the bid. Leverage: funding from the joined meta ballot, with no apparent crowding sign in a single row. Pricing stress: HL mid monitoring exterior mids reasonably than drifting broad.

Rule-based flags on the ledger are stress screens, not accusations. Over the 7-day window, percentile flags relaxation on a firmer baseline than the unique 32 h pilot, however nonetheless in need of the 30-day goal; a 30-day archive stays the precise goal for any market-structure declare.

What stays hidden

Even with a working collector, the outsider nonetheless doesn’t see maker intent, true queue precedence, non-public latency, account-level margin distribution, the complete liquidation path, or risk-engine thresholds.

Public depth can disappear with out a commerce. Public fills carry no maker labels. Cross-venue foundation diverges for causes that aren’t robotically mispricing or routing alpha — the CPI row above is one occasion of a foundation spike with a believable however unverified rationalization.

That incompleteness just isn’t a footnote to scrub up later; it’s a lot of the level of retaining the ledger in any respect. What the ledger is nice for just isn’t seeing the whole lot, however recording precisely what entered the artifact and what stayed outdoors it, and doing that repeatedly sufficient that the boundary itself turns into measurable over time as a substitute of guessed at from one screenshot.

Reconstructing the general public ebook is beneficial not as a result of it restores the venue’s full inside reality, however as a result of it turns an opaque stream right into a state object that may be monitored, in contrast, and stress-tested — the unfold and depth spikes in Fig. 2 double as alert thresholds, and the flat-OI-plus-volume-burst learn in Fig. 4 is one occasion of narrowing an evidence, not simply describing a chart. That is sufficient to help alerting, occasion attribution, and execution or threat choices, without having a accomplished image of maker intent behind them.

Closing

The purpose was by no means Bunni itself. It’s the object an auditor has to comply with.

On the AMM facet, the dwell questions are dynamic charges, hooks, and LP loss surfaces — state that solely is smart learn throughout a sequence. On the CLOB facet, the dwell questions are a transferring ebook, funding and OI, mark-oracle premium, foundation, and the hidden venue state behind them. Each lanes fail the identical manner when the audit object is left obscure: reasoning ahead from a screenshot.

A public ebook doesn’t resolve the audit drawback a lot as relocate it. The subsequent test on this knowledge just isn’t a much bigger dashboard — it’s whether or not a 30-day model of the identical ledger holds up the CPI-basis learn above as a repeatable sample (macro print → quantity burst → foundation spike → flat OI) reasonably than a one-window coincidence.

Appendix: assortment and reproducibility

• Window: 2026–07–13 → 2026–07–19 UTC (7 days, 168 h). Cash: BTC, ETH, SOL — roughly 112,600 rows every. This was the longest stretch in a ~2-week assortment run with no reference-feed or WebSocket outage inside it; these gaps present up elsewhere within the run as lacking rows in Fig. 4, not as a fabricated foundation studying.
• Limitations: seen l2Book ranges solely; nearest-prior be part of for perp meta and reference mids, dropped reasonably than carried ahead previous 5 minutes of staleness; a 7-day run, not but the 30-day market-structure examine this factors towards.
• Copy: Gist appendix (archive_io.py, collect_ws_ledger.py, collect_ref_mids.py, build_ledger.py, build_figures.py).
• Bunni autopsy: weblog.bunni.xyz
• Jul 14 CPI/BTC context: CoinDesk

This submit was initially revealed on my private weblog: https://egpivo.github.io/2026/07/26/when-the-book-keeps-moving.html

---

When the E book Retains Transferring. What Hyperliquid Lets Outsiders Reconstruct. was initially revealed in The Capital on Medium, the place individuals are persevering with the dialog by highlighting and responding to this story.

Supply hyperlink