Hyperliquid
Hyperliquid runs its order book on its own L1 chain, so every order, cancel and fill is public along with the address that sent it, and participant attribution comes straight from the source. We have recorded it from Tokyo and Ireland since November 2025, and it is the first venue we ship.
What we plan to offer on Hyperliquid.
Early access Q1 2027 · GA Q2 2027. Coverage includes every listed perpetual, about 190 today.
Hyperliquid's HIP-1 spot markets are outside the initial scope. Partner votes will decide whether they are added after Phase 1.
All USDC-margined perpetuals, with delisted markets kept in the archive.
Hourly funding with the premium and oracle price used for each settlement.
Snapshots and deltas rebuilt from the node's order state, every block.
Every add, modify, cancel and fill, keyed by order id (oid).
L3 plus the user address on every order, taken from the chain.
How Hyperliquid data arrives.
We run non-validating Hyperliquid nodes in both regions and read order statuses, fills and book state from the node, alongside the public WebSocket API.
- Venue type
- On-chain perpetuals exchange
- Funding interval
- Every hour, on the hour (
interval_s = 3600) - Book checksum
- Each L2 snapshot is checked against the book we rebuild from L3 events.
- Sequence
- L1 block height plus the event's index inside the block
- Snapshots
- A full-depth book snapshot at the top of every UTC hour (the 00:00 snapshot opens each daily file), plus the venue's own snapshots on reconnect, flagged with
is_snapshotandsnapshot_reason - Timestamps
- Milliseconds (block time) in
ts_exchange.ts_captureis int64 nanoseconds from a PTP-disciplined clock. - Regions
- Tokyo (ap-northeast-1) primary, Ireland (eu-west-1) second
- Participant id
- User address (20-byte hex), as recorded on chain
| Market | venue_symbol | symbol |
|---|---|---|
| Perpetual | BTC | BTC-PERP |
| Perpetual | ETH | ETH-PERP |
| Perpetual (1,000 units) | kPEPE | 1000PEPE-PERP |
Hyperliquid perpetuals are margined in USDC. Because the venue lists a single linear contract per asset, it resolves to BTC-PERP; BTC-USDC-PERP is accepted as an alias, and instruments.settle records USDC. The full rules are in symbology.
- Liquidations are flagged on the fill itself, with the liquidated address, so
liquidationsandbook_l4join ontrade_id. - Vault addresses, including HLP, carry
entity_type = protocolinchain_entities, so with chain intelligence vault market-making flow inbook_l4can be separated from user flow. - Funding, open interest and the oracle price come from the same block, so
fundingandmark_indexsharets_exchange.
Where history starts.
Every Hyperliquid dataset starts in November 2025, when our Tokyo and Ireland capture began. Every row carries source = "fdc_capture"; order books are never backfilled from any other source.
| Table | Offered | History from | source | Note |
|---|---|---|---|---|
trades | ● | November 2025 | fdc_capture | |
candles | ● | November 2025 | fdc_capture | |
quotes | ● | November 2025 | fdc_capture | |
book_l2 | ● | November 2025 | fdc_capture | |
book_l3 | ● | November 2025 | fdc_capture | |
book_l4 | ● | November 2025 | fdc_capture | |
funding | ● | November 2025 | fdc_capture | |
open_interest | ● | November 2025 | fdc_capture | |
liquidations | ● | November 2025 | fdc_capture | |
mark_index | ● | November 2025 | fdc_capture | |
extended | ● | November 2025 | computed from fdc_capture | |
instruments | ● | November 2025 | venue reference data | |
gaps | ● | November 2025 | fdc_capture |
History dates are targets. Gaps that survive the two-region merge are listed in the gaps table and never filled. See data quality.
Derived fields on Hyperliquid.
Extended fields are computed on ts_capture and published on a 100 ms grid. A field is available on a venue when its source data is.
Query it.
The same calls work on every venue; only venue and symbol change. Endpoints go live with Phase 1, and the v1 spec is a draft until then.
from fdc import Client
fdc = Client(api_key="fdc_live_...")
# L4 order events with participant ids
book = fdc.book(
venue="hyperliquid",
symbol="BTC-PERP",
depth="L4",
start="2026-03-02",
end="2026-03-02T01:00:00",
)
df = book.to_polars()
# funding at every settlement, then live
funding = fdc.funding(venue="hyperliquid", symbol="BTC-PERP",
start="2026-03-02", live=True)curl -H "Authorization: Bearer fdc_live_..." \
"https://api.financedatacloud.com/v1/book/l4?venue=hyperliquid&symbol=BTC-PERP&start=2026-03-02T00:00:00Z&end=2026-03-02T00:05:00Z"{"op":"subscribe","channel":"book_l4","venue":"hyperliquid","symbol":"BTC-PERP"}aws s3 cp \
s3://fdc-archive/book_l4/venue=hyperliquid/date=2026-03-02/BTC-PERP.parquet .Compare with.
On-chain perpetuals exchange. Planned, subject to a data agreement with dYdX.
View coverageCentralized exchange. Planned, subject to a data agreement with Binance.
View coverageCentralized derivatives exchange. Planned, subject to a data agreement with Deribit.
View coverageShape what ships next.
Pre-registered partners get early access to Hyperliquid data in Q1 2027 and pre-sale pricing for their first 12 months.
EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →