AymarData
PolymarketHistory from 2025-06-01sol-updown-4h

Polymarket SOL Up/Down 4h historical order book & trade data

2.09M order-book and trade events for SOL 4-hour Up/Down markets since 2025-06-01 — about 4,091 events a day across 6 windows.

Coverage

SOL Up/Down 4h data coverage

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

History start

2025-06-01

512 days of history

Events recorded

2,094,840

≈ 2.09M as of 2026-10-25

Avg events / day

4,091

book snapshot · book delta · trade · resolution

Update frequency

Book deltas and trades streamed as they occur; 6 new windows every UTC day

Daily activity · last 30 days

SOL Up/Down 4h events/day: 30-day series, average 4,091 events/day, low 2,636, high 9,159.
low 2,636avg 4,091high 9,159

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

About this market

What is SOL Up/Down 4h?

SOL 4-hour windows capture a whole session of Solana ecosystem news, and the book tends to stay wide until the third hour when direction becomes clearer. Four-hour windows run on fixed boundaries, giving six markets a day. Each window spans a regional trading session — Asia, Europe, the US morning — so the Up/Down binary is effectively a bet on who wins that session.

Solana is the volatile one of the family. SOL's price follows on-chain activity — memecoin launches, launchpad volume, validator-client news — and it frequently moves in bursts rather than smoothly. Over a 4-hour horizon that means more windows that look decided early and then reverse, and a book whose resting liquidity retreats quickly when volatility rises.

With only six windows a day the sample size grows slowly, but each window carries real information: the Up price moves in steps as new data arrives, and liquidity providers show up with size. These windows are good for testing trend-following signals and for studying how the book anchors to intraday session behaviour.

What moves SOL 4h Up/Down

  • Memecoin and launchpad turnover, which drives fee revenue and speculative demand together
  • Network incidents and validator-client upgrades
  • Window structure: regional session handovers — Asia into Europe into the US — which is where intraday direction usually changes

Schema

SOL Up/Down 4h fields and sample rows

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

FieldTypeDescription
ts_exchangestringExchange timestamp (ISO-8601, ms)
ts_recvstringAymarData receive timestamp
marketstringWindow slug: <family>-<window start unix>
outcomestring"up" or "down" token
event_typestringlast_trade_price | price_change | book
sidestring"buy" | "sell" for trades, "bid" | "ask" for book events
pricenumberProbability price, 0–1
sizenumberShares traded or resting size at the level

Sample rows

ts_exchangets_recvmarketoutcomeevent_typesidepricesize
2026-10-22T14:41:08.044Z2026-10-22T14:41:08.075Zsol-updown-4h-1792670400uplast_trade_pricebuy0.48144
2026-10-22T14:41:08.713Z2026-10-22T14:41:08.758Zsol-updown-4h-1792670400downprice_changeask0.532560
2026-10-22T14:41:09.000Z2026-10-22T14:41:09.044Zsol-updown-4h-1792670400uplast_trade_pricesell0.4756

Illustrative rows for sol-updown-4h. Market is the window slug (sol-updown-4h-<start unix>); prices are probabilities between 0 and 1.

Code

Pull SOL Up/Down 4h in Python, cURL or MCP

Market id: sol-updown-4h. 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 Up/Down 4h: every trade in one 4-hour window
trades = requests.get(
    f"{API}/trades",
    headers=H,
    params={
        "source": "polymarket",
        "market": "sol-updown-4h",
        "outcome": "up",
        "start": "2026-10-22T12:00:00Z",
        "end": "2026-10-22T16:00:00Z",
        "limit": 500,
    },
    timeout=30,
).json()["data"]
print(len(trades), trades[0]["price"], trades[-1]["price"])

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

FAQ

SOL Up/Down 4h: common questions

What do the SOL 4h windows cover?

Six fixed four-hour windows per day, each of which spans a regional trading session. sol-updown-4h markets resolve independently of the shorter windows, so you can compare a 4h book with the four 1h books inside it.

Is there enough SOL 4h history for a backtest?

Yes — six windows a day since 2025-06-01 is about 3,072 resolved markets. That is thinner than 5m or 15m, but each window carries many more book updates, so it works well for per-window features.

What moves the SOL 4h Up/Down price most?

Two things dominate. First, memecoin and launchpad turnover, which drives fee revenue and speculative demand together. Second, network incidents and validator-client upgrades. On top of that sits the structural driver of every 4-hour window: regional session handovers — Asia into Europe into the US — which is where intraday direction usually changes. Liquidity here is thinner than BTC and ETH, with visible gaps between price levels in quiet periods.

How does SOL 4h Up/Down compare with the SOLUSDT order book on Binance?

Binance is where price discovery happens; Polymarket prices a probability on top of it. Joining sol-updown-4h with Binance SOLUSDT spot and perp ticks on timestamp lets you measure how many milliseconds the Up price lags a spot move. See the Binance SOL spot and perp pages for the matching feeds.

How big is the sol-updown-4h dataset?

About 2.09M events recorded since 2025-06-01, or roughly 4,091 events a day across about 3,072 windows. Every event carries both exchange and receive timestamps.

Backtest SOL Up/Down 4h with real tick data

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