Hyperliquid Trade Records and Order Book Snapshots
Summary
This document outlines the data a Hyperliquid node can write for market and network activity. It describes where transaction blocks, periodic state snapshots, trades, and miscellaneous events are stored. The listed event types include staking activity, validator rewards, funding distributions, and spot transfers.
The trade example shows fields for the traded asset, side, timestamp, price, size, transaction hash, and the two counterparties. Each counterparty record can include starting position, order ID, and optional TWAP or client order IDs. The document also explains that an L4 snapshot contains full order details at each price level and can serve as a starting point for applying subsequent order status updates. Orders at a price are time-sorted, with trigger orders placed last. This is a data-format overview rather than a trading method; several sections name data categories without giving their schemas, and it does not explain how to interpret or validate the records.
Key ideas
- Trade records identify the asset, side, time, price, size, and transaction hash.
- Each trade includes buyer and seller details, including starting position and order identifiers.
- L4 snapshots preserve full order details and can initialize a live book reconstructed from order updates.
- Trigger orders appear after other orders at the same price level.
- The document names several data streams but omits their detailed schemas.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.