MAINNEAT

Where does the terminal get its data?

Understand public streams, missing data, builder labels and browser collection limits.

By Mainneat / Reviewed / Independent documentation

Where do ordinary trades come from?

The browser subscribes to Hyperliquid public trade streams after discovering market metadata. Data enrichment loads separately. Wallet names, builder names and liquidations can have different sources and freshness from the trade itself.

Why does the number of markets change?

Coverage follows the selected tape family and current discovered metadata. Native perps, HIP-3 perps, spot pairs and outcomes are different sets. Newly listed, halted or unavailable markets can change the counts.

What does a blank builder mean?

A dash can mean that no builder was confirmed or that supporting data is unavailable. The terminal does not infer a builder from the market deployer. A directory name labels an address only after attribution is supported.

What happens if the connection drops?

The client reconnects, but public replay is not a complete backfill guarantee. Some trades may be missed. Session totals and local order-flow indicators describe received data and should be read with any gap notice.

Can I use this as an audited historical database?

No. The browser retains bounded buffers and does not reconstruct every block. Research requiring complete history, exact liquidation coverage or historical book depth needs a separately validated collection source.

Sources and methodology

Protocol details refer to the official sources below. Terminal behavior describes this site's implementation and its stated coverage limits. Examples are illustrative.

Open the related terminal view

Related guides