File size: 6,954 Bytes
645f73c
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
---
license: mit
task_categories:
  - tabular-classification
language:
  - en
tags:
  - polymarket
  - prediction-markets
  - trading
  - mean-reversion
  - finance
size_categories:
  - n<1K
---

# cross-signal-data

[![PyPI](https://img.shields.io/pypi/v/cross-signal-data.svg)](https://pypi.org/project/cross-signal-data/)
[![Python](https://img.shields.io/pypi/pyversions/cross-signal-data.svg)](https://pypi.org/project/cross-signal-data/)
[![HuggingFace](https://img.shields.io/badge/🤗-HuggingFace-yellow.svg)](https://huggingface.co/datasets/manja316/cross-signal-data)
[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)

**The labeled Polymarket crash-recovery dataset behind a 80.2% win-rate live trading bot.**

308 closed trades. Real Polymarket markets. Real entry triggers. Real outcomes. Public for anyone who wants to build their own mean-reversion bot, replicate our results, or prove us wrong.

## What's in here

A single CSV (`data/crashes_v1.csv`) with one row per closed trade on Polymarket where the [crash-recovery bot](https://github.com/LuciferForge/polymarket-crash-bot) entered. Each row has:

- The market (public Polymarket `market_id` and question text)
- The signal (`pre_crash_high`, `entry_price`, `drop_pct`)
- The outcome (`exit_price`, `exit_reason`, `pnl_usd`, `is_profitable`)
- Time features (`entry_hour_utc`, `entry_dow`, `hold_hours`)

| Stat | Value |
|------|-------|
| Total trades | 308 |
| Profitable | 247 (80.2%) |
| Date range | March 2026 – April 2026 |
| Median hold | ~3 hours |
| Avg drop_pct at entry | ~22% |
| Avg recovered_to_pct_of_high | ~85% |

| Exit reason | Count |
|-------------|-------|
| RECOVERY (price came back) | 235 |
| TIMEOUT_48H (held 48h, exited) | 62 |
| TIMEOUT (early TIMEOUT exit) | 11 |

## Why this exists

Most prediction-market datasets are either:
- **Synthetic** (generated for academic papers, no real money behind them), or
- **Aggregate** (volume, liquidity at hourly resolution — useless for tactical signals)

This is neither. It's the actual labeled examples of a single specific signal — *Polymarket markets that crashed N% from a recent high* — paired with the actual outcome of trading the recovery. If you want to study whether mean-reversion works on prediction markets, this is the data.

## Install

```bash
pip install cross-signal-data
```

## Quick use (Python)

```python
from cross_signal_data import load

df = load()
print(df.shape)              # (308, 19)
print(df.columns.tolist())   # full list of fields

# Filter to RECOVERY-only trades
recovered = df[df["exit_reason"] == "RECOVERY"]

# What entry-price bucket has the best win rate?
buckets = df.groupby(df["entry_price"].round(2)).agg(
    n=("trade_id", "count"),
    win_rate=("is_profitable", "mean"),
)
print(buckets)
```

If you don't have pandas:

```python
from cross_signal_data import load
rows = load(as_pandas=False)  # list of dicts
print(len(rows), rows[0])
```

## Quick use (any language)

The file is plain CSV. Just download it:

```bash
curl -o crashes_v1.csv https://raw.githubusercontent.com/LuciferForge/cross-signal-data/main/data/crashes_v1.csv
```

## Schema

See [`docs/schema.md`](docs/schema.md) for full column-by-column documentation.

Key columns:
- `entry_price` — the price-per-share when the bot entered (0–1)
- `pre_crash_high` — the recent local-window high
- `drop_pct``(pre_crash_high − entry_price) / pre_crash_high × 100`
- `exit_reason``RECOVERY`, `TIMEOUT_48H`, `TIMEOUT`, or `STOP`
- `is_profitable` — 1 if `pnl_usd > 0` else 0
- `recovered_to_pct_of_high``exit_price / pre_crash_high × 100`

## Methodology

See [`docs/methodology.md`](docs/methodology.md) for:
- How the crash signal is defined
- Entry/exit rules
- Known biases (survivorship: only triggers that fired are recorded; a different threshold might surface different examples)
- What's NOT in the data (slippage cost — see [pnl-truthteller](https://github.com/LuciferForge/pnl-truthteller) for the slippage layer)

## Reproducibility

The script that generated this dataset is in [`scripts/extract.py`](scripts/extract.py). Anyone with the source `positions.json` from the bot can rerun it:

```bash
python scripts/extract.py \
    --positions /path/to/positions.json \
    --output data/crashes_v1.csv
```

## Baseline notebook

[`notebooks/baseline_model.py`](notebooks/baseline_model.py) trains a logistic regression and random forest on the dataset to predict `is_profitable`.

Result: **~79.9% cross-validated accuracy** with simple features — essentially matching the bot's 80.2% WR. Translation: most of the alpha is **in the entry trigger itself** (which already filters to high-WR setups), not in further feature engineering. If you want to beat this dataset, you almost certainly need features the bot doesn't currently log (orderbook depth, market category, time-to-resolution).

Top feature importances from the random forest:

| Feature | Importance |
|---------|-----------:|
| `drop_pct` | 0.254 |
| `shares` | 0.200 |
| `entry_price` | 0.174 |
| `pre_crash_high` | 0.171 |
| `entry_hour_utc` | 0.110 |
| `entry_dow` | 0.059 |

A clean, exploitable insight from the diurnal column: win rate at hours 16, 21, 22 UTC reaches ~100% (small samples though); hour 8 UTC dips to ~55%. Off-peak hours are punishing. Adjust your live-firing schedule accordingly.

```bash
pip install cross-signal-data[ml]
python notebooks/baseline_model.py
```

## Versioning

| Version | Date | Trades | Notes |
|---------|------|--------|-------|
| v1 | 2026-04-28 | 308 | Initial public release |

Future versions will add more trades, more features (orderbook depth at entry, market category, time-to-resolution) and possibly per-market metadata. Pin to a specific version if reproducibility matters: `load(version="v1")`.

## License

**Code: MIT.** Use the loader, the extraction script, and the baseline notebook however you want.

**Data: MIT.** Public on-chain prediction market data, transformed into a labeled dataset. Cite if you use it in research.

## Citation

```bibtex
@dataset{cross_signal_data_2026,
    title  = {cross-signal-data: Polymarket crash-recovery labeled dataset},
    author = {LuciferForge},
    year   = {2026},
    url    = {https://github.com/LuciferForge/cross-signal-data}
}
```

## About the author

Built by [LuciferForge](https://github.com/LuciferForge), running a [public-audited Polymarket crash bot](https://github.com/LuciferForge/polymarket-crash-bot) (308 closed trades, 80.2% WR, all data here). Also runs:
- [polymarket-mcp](https://github.com/LuciferForge/polymarket-mcp) — MCP server for live Polymarket data
- [pnl-truthteller](https://github.com/LuciferForge/pnl-truthteller) — slippage audit tool
- [polymarket-v2-migration](https://github.com/LuciferForge/polymarket-v2-migration) — V1→V2 cookbook
- [protodex.io](https://protodex.io) — public MCP-server index