Hyperliquid ETH perpetual: order book, trades & funding data
704K trade, L2 and funding events for the ETH perp on Hyperliquid, recorded live since 2026-10-01 — about 28,160 events a day.
Coverage
ETH 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
704,000
≈ 704K as of 2026-10-25
Avg events / day
28,160
trade · L2 book update · funding
Update frequency
Trades and L2 book updates in real time; funding settled hourly
Daily activity · last 25 days
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 ETH perp?
ETH is the venue's second pillar: large on-chain wallets route size through it, so the tape often carries single prints bigger than anything outside BTC. AymarData has been recording the ETH perpetual on Hyperliquid since 2026-10-01 and holds 704K events so far, about 28,160 a day. History is forward-only: we record live and do not backfill.
Ether is the settlement asset of the largest smart-contract ecosystem and trades as a higher-beta cousin of Bitcoin. On Hyperliquid, ETH is moved by staking and ETF-flow headlines that change how much supply is liquid, and by DeFi stress, because ETH collateral gets liquidated when lending markets de-risk. 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 28,160 events a day, the ETH 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 ETH on Hyperliquid
- Staking and ETF-flow headlines that change how much supply is liquid
- DeFi stress, because ETH collateral gets liquidated when lending markets de-risk
- The ETH/BTC ratio, which rotates capital between the two majors on risk-on and risk-off days
Schema
ETH perp fields and sample rows
The same columns are returned by the API and in Parquet and CSV files.
| Field | Type | Description |
|---|---|---|
| ts_ms | int64 | Venue event time, Unix milliseconds |
| symbol | string | Hyperliquid coin name, here ETH |
| event_type | string | trade | l2_update | funding |
| side | string | buy / sell for trades; bid / ask for book levels; null on funding |
| price | number | Trade price or book level in USD |
| size | number | Size in coin units; null on funding |
| funding_rate | number | null | Hourly funding rate on funding events, else null |
Sample rows
| ts_ms | symbol | event_type | side | price | size | funding_rate |
|---|---|---|---|---|---|---|
| 1792677599431 | ETH | trade | buy | 2643.5 | 3.214 | null |
| 1792677599803 | ETH | l2_update | bid | 2643.9 | 10.35 | null |
| 1792677600505 | ETH | funding | null | 2643.9 | null | 0.00000313 |
Illustrative rows for ETH on Hyperliquid; prices in USD, shown for schema purposes. Funding appears on funding events.
Code
Pull ETH perp in Python, cURL or MCP
Market id: ETH. 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"}
# ETH perp: ten minutes around the 14:00 UTC hourly funding
trades = requests.get(
f"{API}/trades",
headers=H,
params={
"source": "hyperliquid",
"market": "ETH",
"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": "ETH",
"at": "2026-10-22T14:00:00Z",
"depth": 10,
},
timeout=30,
).json()
print(book.get("spread"), len(trades))FAQ
ETH perp: common questions
Is the ETH perp on Hyperliquid liquid enough for execution research?
Yes. With about 28,160 events a day on ETH, 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 ETH perp on Hyperliquid?
Staking and ETF-flow headlines that change how much supply is liquid, and DeFi stress, because ETH collateral gets liquidated when lending markets de-risk. Hyperliquid's hourly funding and on-chain liquidations amplify both effects. ETH is the venue's second pillar: large on-chain wallets route size through it, so the tape often carries single prints bigger than anything outside BTC.
How far back does ETH 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 704K events at the time of this page. Coverage grows every day.
How is funding stored for ETH?
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 ETH.
How does the ETH perp compare with Binance's?
Join Hyperliquid ETH with the Binance ETHUSDT 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.
Related
Related markets and next steps
Binance ETHUSDT perp
Centralized-venue comparison
HYPE perp
Related Hyperliquid perp
ZEC perp
Related Hyperliquid perp
SOL perp
Related Hyperliquid perp
Polymarket: ETH Up/Down 15m
Prediction-market view of the same asset
Binance spot: ETHUSDT spot
Binance spot order book
Kalshi: KXETHD ETH Daily
Kalshi contracts on the same asset
← All hyperliquid data
Parent hub for Hyperliquid
Pricing →
Builder, Pro and Enterprise plans
Backtest ETH perp with real tick data
Get an API key, pull your first window and join it with the other sources in the catalog.