AymarData
HyperliquidLive recording · forward-onlyBTC

Hyperliquid BTC perpetual: order book, trades & funding data

1.06M trade, L2 and funding events for the BTC perp on Hyperliquid, recorded live since 2026-10-01 — about 42,240 events a day.

Coverage

BTC perp data coverage

What is recorded, how often it updates and how much there is.

Recording since

2026-10-01

25 days so far · no backfill

Events recorded

1,056,000

≈ 1.06M as of 2026-10-25

Avg events / day

42,240

trade · L2 book update · funding

Update frequency

Trades and L2 book updates in real time; funding settled hourly

Daily activity · last 25 days

BTC perp events/day: 25-day series, average 42,240 events/day, low 22,173, high 63,531.
low 22,173avg 42,240high 63,531

Indicative daily event volume, last 25 days to 2026-10-25. Shape modeled from collector stats; mean matches the average events/day above.

About this market

What is BTC perp?

BTC is Hyperliquid's anchor market: the deepest book on the venue, and the one that sets the tone for funding, open interest and liquidations across the whole exchange. AymarData has been recording the BTC perpetual on Hyperliquid since 2026-10-01 and holds 1.06M events so far, about 42,240 a day. History is forward-only: we record live and do not backfill.

Bitcoin is the market's reserve asset and the benchmark every other crypto instrument is quoted against. On Hyperliquid, BTC is moved by US spot-ETF creations and redemptions, which show up as persistent one-way flow around the New York cash open, and by macro prints (CPI, payrolls, FOMC) that reprice the dollar and real yields within seconds. The venue adds its own mechanics: funding is paid hourly rather than every eight hours, and positions are on-chain, so liquidation clusters and large wallets are visible rather than inferred.

At about 42,240 events a day, the BTC perp is dense enough for execution studies: replay depth against trades, track hourly funding resets, and see how on-chain wallet flow changes the order book. Because Hyperliquid settles on-chain, the venue's own liquidations are part of the story, not noise.

What moves BTC on Hyperliquid

  • US spot-ETF creations and redemptions, which show up as persistent one-way flow around the New York cash open
  • Macro prints (CPI, payrolls, FOMC) that reprice the dollar and real yields within seconds
  • Liquidation cascades on leveraged venues, which turn a 1% move into a 3% wick

Schema

BTC perp fields and sample rows

The same columns are returned by the API and in Parquet and CSV files.

FieldTypeDescription
ts_msint64Venue event time, Unix milliseconds
symbolstringHyperliquid coin name, here BTC
event_typestringtrade | l2_update | funding
sidestringbuy / sell for trades; bid / ask for book levels; null on funding
pricenumberTrade price or book level in USD
sizenumberSize in coin units; null on funding
funding_ratenumber | nullHourly funding rate on funding events, else null

Sample rows

ts_mssymbolevent_typesidepricesizefunding_rate
1792677599629BTCtradebuy672890.1341null
1792677599860BTCl2_updatebid673050.071null
1792677600641BTCfundingnull67305null0.00000208

Illustrative rows for BTC on Hyperliquid; prices in USD, shown for schema purposes. Funding appears on funding events.

Code

Pull BTC perp in Python, cURL or MCP

Market id: BTC. Export AYMARDATA_API_KEY from your dashboard, then run the Python requests example.

import os
import requests

API = "https://api.aymardata.com/v1"
KEY = os.environ["AYMARDATA_API_KEY"]  # export AYMARDATA_API_KEY=ad_live_…
H = {"Authorization": f"Bearer {KEY}", "User-Agent": "aymardata-docs/1.0"}

# BTC perp: ten minutes around the 14:00 UTC hourly funding
trades = requests.get(
    f"{API}/trades",
    headers=H,
    params={
        "source": "hyperliquid",
        "market": "BTC",
        "start": "2026-10-22T13:55:00Z",
        "end": "2026-10-22T14:05:00Z",
        "limit": 500,
    },
    timeout=30,
).json()["data"]
funding = [t for t in trades if t["event_type"] == "funding"]
print(funding[0]["funding_rate"] if funding else "no funding event in window")

book = requests.get(
    f"{API}/book",
    headers=H,
    params={
        "source": "hyperliquid",
        "market": "BTC",
        "at": "2026-10-22T14:00:00Z",
        "depth": 10,
    },
    timeout=30,
).json()
print(book.get("spread"), len(trades))

FAQ

BTC perp: common questions

Is the BTC perp on Hyperliquid liquid enough for execution research?

Yes. With about 42,240 events a day on BTC, you can replay order-book updates against trades and measure slippage by size. Remember that this is a forward-only recording, so the window is shorter than our Binance history.

What moves the BTC perp on Hyperliquid?

US spot-ETF creations and redemptions, which show up as persistent one-way flow around the New York cash open, and macro prints (CPI, payrolls, FOMC) that reprice the dollar and real yields within seconds. Hyperliquid's hourly funding and on-chain liquidations amplify both effects. BTC is Hyperliquid's anchor market: the deepest book on the venue, and the one that sets the tone for funding, open interest and liquidations across the whole exchange.

How far back does BTC data on Hyperliquid go?

Recording started 2026-10-01, and it is forward-only — we do not backfill Hyperliquid. That is about 25 days and 1.06M events at the time of this page. Coverage grows every day.

How is funding stored for BTC?

As separate events (event_type=funding) with a funding_rate field, in the same time-ordered stream as trades and L2 updates. Hyperliquid pays funding hourly, so expect 24 funding events a day for BTC.

How does the BTC perp compare with Binance's?

Join Hyperliquid BTC with the Binance BTCUSDT perp on ts_ms to measure basis, lead-lag and funding differences. Binance history runs from 2025-06-01; Hyperliquid from 2026-10-01, so overlap starts there.

Backtest BTC perp with real tick data

Get an API key, pull your first window and join it with the other sources in the catalog.