Skip to content

Open benchmark

Models
against
consensus

The model's forecast against the Polymarket price.

  • The forecast is fixed in the Bitcoin network within minutes
  • Afterwards we check it against the market
  • Six markets, the history of misses is open

Market verticals

One verification protocol: the algorithm's probability is locked in, the market price is frozen with it, and the track record stays open.

  • Crypto & finance

    Crypto assets, macro indices, commodity markets and metals against Polymarket.

    CryptoFinance
  • Weather

    Daily temperature targets in major cities against Polymarket weather contracts.

    Weather
  • Politics & tech

    Electoral cycles and company capitalisation rankings against Polymarket.

    PoliticsTech
  • Sports

    Matches and tournaments on Polymarket: the model against the market price.

    Sports
Forecast journal
Rows:
ClaimUsMarketDisagreementDueOutcome
ETHUSDT $1,800 YES6466−2Nov 20pending
ETHUSDT $2,200 NO02−2Nov 20pending
ETHUSDT $1,600 YES9495−1Nov 20pending
BTCUSDT $62,000 YES8482+2Nov 20pending
XRPUSDT $0.9 YES8277+5Nov 20pending
ETHUSDT $1,500 YES9796+1Nov 20pending
ETHUSDT $1,900 NO2026−6Nov 20pending
ETHUSDT $2,000 NO811−3Nov 20pending
ETHUSDT $2,100 NO34−1Nov 20pending
BTCUSDT $60,000 YES9185+6Nov 20pending

1–10 of 909

⇪⇪
touch: settlement happens the moment the price first reaches the level — the outcome can be decided long before the deadline.
▲▼
close: settled on the price at the stated date, and on that price alone.
⧓
range: the price landing between the two levels counts.
✅❌
the outcome of the call: our own call checked against the fact — it came true or it did not.

Vertical · Binance price corridors

The sealed forecast journal

Every price forecast — a 50% core and an 80% band — is hashed with SHA-256 and stamped in Bitcoin before the outcome. Below: calibration, the latest resolved forecast and the full journal.

Fig. 1 · How often what we say comes true

updated with every resolved forecast

ModelMarketHonest lineRecent forecast

How often it happened

0%20%40%60%80%100%Market 0% – 10%: 102 of 1,820Market 10% – 20%: 197 of 1,458Market 20% – 30%: 346 of 1,393Market 30% – 40%: 495 of 1,432Market 40% – 50%: 517 of 1,144Market 50% – 60%: 355 of 663Market 60% – 70%: 132 of 193Market 70% – 80%: 36 of 48Market 80% – 90%: 46 of 62Market 90% – 100%: 186 of 201Model 0% – 10%: 398 of 2,447Model 10% – 20%: 371 of 1,479Model 20% – 30%: 385 of 1,348Model 30% – 40%: 404 of 1,254Model 40% – 50%: 306 of 882Model 50% – 60%: 183 of 475Model 60% – 70%: 79 of 179Model 70% – 80%: 48 of 78Model 80% – 90%: 41 of 55Model 90% – 100%: 197 of 217The recently resolved forecast is in this group: model 27%244714791348125488247517978552170%20%40%60%80%100%

What the forecast said — the probability of “yes”

bar — how many of the model's forecasts are in the group

How often the event happened in each group of forecasts
SaidModelMarket
0% – 10%398 of 2,447 — 16%102 of 1,820 — 6%
10% – 20%371 of 1,479 — 25%197 of 1,458 — 14%
20% – 30%385 of 1,348 — 29%346 of 1,393 — 25%
30% – 40%404 of 1,254 — 32%495 of 1,432 — 35%
40% – 50%306 of 882 — 35%517 of 1,144 — 45%
50% – 60%183 of 475 — 39%355 of 663 — 54%
60% – 70%79 of 179 — 44%132 of 193 — 68%
70% – 80%48 of 78 — 62%36 of 48 — 75%
80% – 90%41 of 55 — 75%46 of 62 — 74%
90% – 100%197 of 217 — 91%186 of 201 — 93%

How to read the chart

  • Dashed line — the honest line: said 30%, happened 30 times in 100.
  • Below the line — the event happened less often than said: the chance of “yes” was set too high. Above — more often: set too low. So right of 50%, a point below the line means too much confidence in “yes”, and left of 50%, a point above the line means too much confidence in “no”.
  • Bars at the bottom — how many forecasts are in the group. The lower the bar, the less the point can be trusted; with fewer than 20, the point is pale.
Model's Brier
0.197
Market's Brier
0.163

Average Brier score · lower is betterThe market is more accurate right now.

Fig. 1. Each point is a group of forecasts with a similar probability. If the model says 70% and is right about 70 times in 100, the point lands on the dashed line. Across — what the forecast said; up — how often it happened. 8,414 forecasts resolved in the Experiment's journal. Market is the Polymarket price at the moment the model recorded its forecast.

Observation · recently resolved

Will the highest temperature in Jeddah be 34°C on November 19?

Polymarket · · outcome “yes” · the model's call did not come true · the market was closer to the outcome

Model
27%
Market
39%
Brier (Model / Market)
0.538 / 0.372

Dataset · The sealed ledger

last sealed 19 Nov, 05:00 UTC

The sealed ledger

Our price forecasts on Binance candles: each is hashed with SHA-256 before it is published and checked against the candle's close.

  1. Step 1Every forecast is written in full, SHA-256 hashed and anchored to the Bitcoin blockchain before it is published.
  2. Step 2We publish a distribution, not a price call: a core 50% zone and a wider 80% band, each with its stated probability.
  3. Step 3The outcome is the Binance close of the minute containing the stated resolution time. No other venue, no re-pick.
  4. Step 4Coverage is the score. The outcome should land inside the core zone about half the time — much more is cowardice, much less is overconfidence, and both are failures.
Forecasts scored · distinct days
4,371
over 108 days
Core 50% coverage (target 50%)
49%
Wide 80% coverage (target 80%)
83%
Median error · sealed & waiting
4.39%
909 pending

These assets move together. Forecasts sealed on one morning are not independent claims — when Bitcoin leaves its band, most of the rest leave theirs on the same candle. That is why the count of distinct days sits next to the count of forecasts, and why coverage is broken out below rather than pooled into one flattering number.

Table 1. Coverage by horizon — actual / target

HorizonCore 50%Wide 80%Mean errorScored
24h57% / 5084% / 80-0.1%1,737
7d54% / 5083% / 80-1.4%1,594
30d28% / 5082% / 80-7.9%1,040

Table 2. Core coverage by asset · scored

  • AAVE43%
  • ADA48%
  • AVAX49%
  • BCH46%
  • BNB50%
  • BTC55%
  • DOGE46%
  • DOT38%
  • ENA45%
  • ETH55%
  • HBAR40%
  • LINK49%
  • LTC43%
  • NEAR45%
  • PAXG27%
  • PEPE52%
  • QNT28%
  • SHIB51%
  • SOL58%
  • SUI44%
  • TAO56%
  • TRX72%
  • UNI52%
  • WLD8%
  • XLM44%
  • XRP44%
  • ZEC56%

Table 3. Latest records · last sealed 19 Nov, 05:00 UTC

AssetCore 50%Wide 80%MedianOutcomeVerdictSHA-256
ZEC30d$1,007–$1,591$846–$1,943$1,258…resolves 22 Nov, 04:01 UTC9ebff0fc60ba
AAVE30d$129–$180$115–$215$152…resolves 21 Nov, 04:01 UTC75140910ecc9
ADA30d$0.1832–$0.2534$0.1577–$0.3191$0.214…resolves 21 Nov, 04:01 UTC17436a994379
AVAX30d$7.86–$11.38$6.66–$15.43$9.37…resolves 21 Nov, 04:01 UTC17a7214139c2
BCH30d$254–$319$224–$362$283…resolves 21 Nov, 04:01 UTC8f0c6ed95d25
BNB30d$688–$874$583–$930$786…resolves 21 Nov, 04:01 UTC1dc5ee0ce47b
BTC30d$76,249–$104,317$69,126–$113,480$87,428…resolves 21 Nov, 04:01 UTC905fd425d418
DOGE30d$0.0682–$0.0925$0.0619–$0.1036$0.0763…resolves 21 Nov, 04:01 UTCcc5718028759
ENA30d$0.1612–$0.2534$0.1232–$0.3622$0.1931…resolves 21 Nov, 04:01 UTCc7ce41035cce
ETH30d$2,171–$2,888$1,886–$3,192$2,464…resolves 21 Nov, 04:01 UTC5ec938ee2bcf

Newest first · showing 861–870 of 909 sealed forecasts

Check it yourself, no need to trust us

Sealed forecasts and their Bitcoin timestamps are kept in an open repository; the exceptions are listed in its description. Download a file and its proof (.ots). On opentimestamps.org, drop the proof first, then the file, and you will see the Bitcoin block it is anchored in.

Open the proof repository

Timestamps by OpenTimestamps · Listed on PolyMart

  • Sealed in Bitcoin minutes after the call. The model probability and the market price share one UTC timestamp.
  • Scored on the fact. Only the oracle's official resolution counts — strictly 0 or 1.
  • Judged by one rule. The Brier score applies to both sides; the lower it is, the sharper the forecast.

How the journal works

Metric lock-in

The algorithm's forecast probability, the contract's spot market price and the expiry date are frozen against a UTC timestamp. Historical records cannot be altered.

Protocol architecture

Frequently asked questions

The system is built on end-to-end auditing and on recording data at the moment of the call. When a forecast is published, the entry receives an immutable UTC timestamp that binds and archives three key parameters together:

  • The model's current predictive probability.
  • The contract's current spot market price on Polymarket.
  • The exact expiration and market resolution date.

The protocol automatically rejects any submission sent after the deadline, and existing entries are protected from being overwritten. The journal is an append-only log: deleting, hiding or retrospectively correcting entries is blocked at the core.

A second, independent verification layer is in place: every page of the pool is indexed by the Wayback Machine. A snapshot taken before trading officially closes is always available for cross-checking against the platform's historical track record.

We use cookies to keep the AI terminals and the payment gateway working and to complete verification. By staying on the site, you agree to our Cookie Policy and Privacy Policy.

By choosing “Accept and continue” you also allow Google Ads advertising cookies, used to measure our ads. They are never used in the user account.