THE LIQUID DATA JOURNALFOUNDATIONAL NOTES / 04 OCT 2026
Foundation notes
5 of 5 foundation notesOpen a note to read · source review 04 Oct 2026
01
Market Structure
The price is only the surface.
A framework for reading price, activity, and positioning together.
1 MIN READFOUNDATION NOTE
+
01 / 01
Four observations, four questions.
Mark price describes the reference used for a perpetual. Volume records activity over a window. Open interest describes outstanding positions. Funding describes a transfer between sides. These measurements answer different questions; none is a complete account of market structure.
01 / 02
What a snapshot cannot tell you.
A single observation cannot establish a change in positioning. Comparing successive, timestamped observations is necessary before describing open interest as rising or falling. Even then, an increase does not identify the motivation of each participant.
01 / 03
Our reading rule.
Liquid Data presents observations before commentary. We keep source values, units, and collection times visible. Any interpretation should name the observations supporting it and the alternative explanations that remain.
02
Token Economics
Follow the mechanism. Then the supply.
Why purchases, balances, and burns need separate records.
1 MIN READFOUNDATION NOTE
+
02 / 01
A mechanism is not a measurement.
The protocol documentation describes the Assistance Fund converting trading fees to HYPE and states that HYPE in the fund is burned. That describes a protocol mechanism. A reconciled historical quantity requires its own evidence.
02 / 02
Holdings are not an event log.
A balance is a state observed at a time. A purchase is an execution. A burn is a supply event. Subtracting two sampled balances cannot, by itself, reconstruct every intervening purchase, movement, and supply change.
02 / 03
Keep the boundaries visible.
Liquid Data separates Assistance Fund purchase history, balance observations, and supply accounting. Saved observations retain their dates, gaps and source boundaries. Totals requiring complete event history remain unavailable. We do not turn a plausible narrative into a numerical estimate.
03
Protocol Mechanics
Two environments. One network.
Understanding the relationship between HyperCore and HyperEVM.
1 MIN READFOUNDATION NOTE
+
03 / 01
Different execution surfaces.
HyperCore hosts the native trading environment. HyperEVM adds an Ethereum-compatible execution environment. HyperEVM blocks form part of Hyperliquid execution and inherit security from HyperBFT consensus.
03 / 02
Fees have their own accounting.
HYPE is the native gas token. HyperEVM documentation distinguishes base-fee burns from priority-fee burns. These paths need explicit treatment when building a ledger, including units, block coverage, and the source of each amount.
03 / 03
A sample needs a boundary.
A set of sampled EVM blocks is not full-chain history. A meaningful total needs a defined first and last block, continuity checks, handling of missing records, and a clearly documented aggregation method.
04
Ecosystem
Read the network in layers.
A map from execution and liquidity to applications and interfaces.
1 MIN READFOUNDATION NOTE
+
04 / 01
Start with the dependencies.
An interface depends on data and execution. An application may depend on liquidity, infrastructure, and other applications. A useful ecosystem map explains these relationships rather than presenting a wall of logos.
04 / 02
Separate access from execution.
Public APIs expose observations. Interfaces organize them for people. The execution layer processes changes to state. Liquid Data stays at the observation layer: it reads public information and does not submit financial actions.
04 / 03
Know what the map leaves out.
This map is an explanatory model. It does not rank applications, imply endorsement, measure total value, or claim to enumerate every participant. Source documentation remains the authority on protocol behavior.
05
Data Coverage
The value of an honest blank.
Missing values, partial histories, and the limits of inference.
1 MIN READFOUNDATION NOTE
+
05 / 01
Unknown is a useful state.
A missing value can mean an unreachable provider, an unsupported field, or a dataset that has never been collected. These are different from an observed zero. Liquid Data keeps the distinction visible with a dash and a contextual status.
05 / 02
Time is part of the observation.
The time a request returns is not always the time of the source observation. Candles carry their own timestamps. Asset-context responses do not provide one global source timestamp. We label the latter with retrieval time rather than inventing a source time.
05 / 03
Coverage is a first-class field.
Provider responses may be bounded or paginated. A successful request does not establish exhaustive history. An archive should record the requested range, returned range, checkpoints, failures, and unresolved gaps before claiming completeness.
Live workspace coverage Sources, refresh rates & boundaries
Hypurrscan HyperCore holder index; not an independently operated full-chain index
Live refresh and archive collection
Data & coverage
Live panels refresh while visible. Protocol research reads the saved daily archive; collection uses a separate authenticated updater. The latest persisted collection and each source’s timestamps are shown in Protocol research. A connected collector and a scheduled successful run are separate states.
ConnectingFeed details
Waiting for streaming market data.
Perpetual contexts and available spot reference prices stream. Individual figures retain their own receipt times. Protocol cards refresh public sources independently; historical charts and issuer reports keep their reporting dates.
