AymarData
HyperliquidLive recording · forward-onlySOL

Hyperliquid SOL perpetual: order book, trades & funding data

308K trade, L2 and funding events for the SOL perp on Hyperliquid, recorded live since 2026-10-01 — about 12,320 events a day.

Coverage

SOL 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

308,000

≈ 308K as of 2026-10-25

Avg events / day

12,320

trade · L2 book update · funding

Update frequency

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

Daily activity · last 25 days

SOL perp events/day: 25-day series, average 12,320 events/day, low 8,281, high 31,761.
low 8,281avg 12,320high 31,761

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 SOL perp?

SOL is the most active major alt on the venue and the favourite instrument for leveraged views on the Solana ecosystem. AymarData has been recording the SOL perpetual on Hyperliquid since 2026-10-01 and holds 308K events so far, about 12,320 a day. History is forward-only: we record live and do not backfill.

Solana is a high-throughput layer-1 whose price tracks on-chain activity, especially memecoin and launchpad volume. On Hyperliquid, SOL is moved by network incidents and validator-client upgrades, and by ETF filings and treasury-company buying that arrive as scheduled headlines. 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 12,320 events a day, the SOL 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 SOL on Hyperliquid

  • Network incidents and validator-client upgrades
  • ETF filings and treasury-company buying that arrive as scheduled headlines
  • Memecoin and launchpad turnover, which drives fee revenue and speculative demand together

Schema

SOL 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 SOL
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
1792677599117SOLtradebuy168.9631.96null
1792677599394SOLl2_updatebid168.98133.9null
1792677600299SOLfundingnull168.98null-0.0000023

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

Code

Pull SOL perp in Python, cURL or MCP

Market id: SOL. 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"}

# SOL perp: ten minutes around the 14:00 UTC hourly funding
trades = requests.get(
    f"{API}/trades",
    headers=H,
    params={
        "source": "hyperliquid",
        "market": "SOL",
        "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": "SOL",
        "at": "2026-10-22T14:00:00Z",
        "depth": 10,
    },
    timeout=30,
).json()
print(book.get("spread"), len(trades))

FAQ

SOL perp: common questions

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

Yes. With about 12,320 events a day on SOL, 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 SOL perp on Hyperliquid?

Network incidents and validator-client upgrades, and ETF filings and treasury-company buying that arrive as scheduled headlines. Hyperliquid's hourly funding and on-chain liquidations amplify both effects. SOL is the most active major alt on the venue and the favourite instrument for leveraged views on the Solana ecosystem.

How far back does SOL 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 308K events at the time of this page. Coverage grows every day.

How is funding stored for SOL?

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 SOL.

How does the SOL perp compare with Binance's?

Join Hyperliquid SOL with the Binance SOLUSDT 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 SOL perp with real tick data

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