Skip to main content

Numinous Crunch Starter Package

Project description

Numinous

Numinous is a real-time binary event forecasting challenge hosted by CrunchDAO at crunchdao.com.

The goal is to predict the probability that real-world events resolve "Yes" — sourced from prediction markets like Polymarket. You don't predict a single outcome; you report your honest probability estimate, and scoring rewards calibration.

Install

pip install crunch-numinous

What You Must Predict

For each event, you receive structured data and must return a probability between 0.0 and 1.0 that the event resolves "Yes":

# Input: event data pushed to your model
{
    "event_id": "polymarket-12345",
    "title": "Will X happen by Y?",
    "description": "...",
    "cutoff": "2026-03-16T00:00:00Z",
    "source": "polymarket",
    "yes_price": 0.65,          # current market price
    "volume_24h": 150000.0,
    "metadata": {}
}

# Output: your probability forecast
{"event_id": "polymarket-12345", "prediction": 0.72}
  • prediction = 1.0 → certain "Yes"
  • prediction = 0.0 → certain "No"
  • prediction = 0.5 → maximum uncertainty

Predictions are clipped to [0.01, 0.99] during scoring.

Scoring

Predictions are evaluated using the Brier score: a strictly proper scoring rule where the optimal strategy is to report your honest probability estimate.

$$ \text{Brier} = (\text{prediction} - \text{outcome})^2 $$

Lower is better.

Score Meaning
0.00 Perfect prediction
0.25 Always predicting 0.5 (no information)
1.00 Worst possible (predicted 1.0, outcome was 0)

Missing predictions are imputed as 0.5 → scored at 0.25. Any model that does useful work should beat this baseline.

Leaderboard ranking is based on a rolling average of Brier scores across all events, evaluated relative to other participants.

Create Your Tracker

A tracker is a model that receives event data and returns probability forecasts. It operates incrementally: events are pushed via feed_update(), and predictions are requested via predict().

To participate, subclass TrackerBase and implement _predict():

from numinous.tracker import TrackerBase


class MyModel(TrackerBase):

    def _predict(self, subject, resolve_horizon_seconds, step_seconds):
        data = self._get_data(subject)
        if not isinstance(data, dict):
            return {"event_id": subject, "prediction": 0.5}

        event_id = data.get("event_id", subject)
        yes_price = data.get("yes_price", 0.5)

        # Your logic here — this example just follows the market
        prediction = yes_price

        return {"event_id": event_id, "prediction": prediction}

How It Works

  1. feed_update(data) is called with new event data — stored automatically by TrackerBase
  2. predict(subject, ...) is called — use self._get_data(subject) to access the latest event data

Available Event Fields

Inside _predict(), self._get_data(subject) gives you:

Field Type Description
event_id str Unique event identifier
title str The question being asked
description str Additional context
cutoff str ISO 8601 resolution deadline
source str Data source (e.g. "polymarket")
yes_price float Current market probability
volume_24h float Recent trading volume
metadata dict Additional source-specific data

Tracker Examples

The package ships with several example trackers to help you get started:

Tracker Strategy
BaselineTracker Always predicts 0.5 — the uninformative prior. Guaranteed Brier score of 0.25.
MarketTracker Returns the current yes_price — the efficient market baseline. Hard to beat consistently.
CalibratedTracker Shrinks market price toward 0.5 using Bayesian shrinkage (α=0.8). Corrects for market overconfidence.
ContrarianTracker Predicts 1.0 - yes_price — bets against the crowd. Wins when markets are wrong.
KeywordTracker Adjusts market price using keyword sentiment from the event title/description. A naive NLP approach.
from numinous.examples import MarketTracker, CalibratedTracker

# Use directly
tracker = MarketTracker()
tracker.feed_update({"event_id": "abc", "yes_price": 0.65, "title": "Will X happen?"})
result = tracker.predict("abc", resolve_horizon_seconds=3600, step_seconds=300)
print(result)  # {"event_id": "abc", "prediction": 0.65}

See numinous/examples/ for full implementations.

General Advice

  • Start with MarketTracker — the prediction market price is a very strong baseline. Most value comes from knowing when and how much to deviate from it.
  • Calibration matters — the Brier score is strictly proper, so reporting honest probabilities is optimal. Don't be overconfident.
  • Use all available signals — title, description, volume, metadata, and time-to-cutoff all carry information.
  • Think about edge cases — events near their cutoff behave differently from events weeks away.
  • Diversify your approach — combining multiple models (market + NLP + time-decay) often outperforms any single strategy.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

crunch_numinous-0.2.0.tar.gz (428.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

crunch_numinous-0.2.0-py3-none-any.whl (431.7 kB view details)

Uploaded Python 3

File details

Details for the file crunch_numinous-0.2.0.tar.gz.

File metadata

  • Download URL: crunch_numinous-0.2.0.tar.gz
  • Upload date:
  • Size: 428.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.9

File hashes

Hashes for crunch_numinous-0.2.0.tar.gz
Algorithm Hash digest
SHA256 c6f5cffbe357ca06b42ee3a752bdbcfd6fa6918fdfc5fba44b7f6d2c081b9f3b
MD5 71652c9a7c8c34d81dbfd8a3bf254052
BLAKE2b-256 8319dc63840396b1c59bcef56f8a33cd09b89a3a71074429b232f200de3fe5e5

See more details on using hashes here.

File details

Details for the file crunch_numinous-0.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for crunch_numinous-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 d4b636d0cea5b1eb127439d09975477ff5d0ab3ce47a583b4b957c46fbeb300f
MD5 346fccf3e3db4a7e334cddaf3c8b9fd4
BLAKE2b-256 b9ab37e3d852f6959cc5e24925d53cb00d284ccb7a21f50f3a533b3dc7bccd72

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page