Week Three — Foundation model vs Brownian motion. Kronos on five-minute BTC.

📊 Full opportunity report: Week Three — Foundation model vs Brownian motion. Kronos on five-minute BTC. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

TL;DR

A recent test comparing Kronos, a foundation model, against Brownian motion for 5-minute BTC forecasts found no significant performance difference. The study suggests current learned models may not outperform traditional stochastic assumptions in this context.

Recent testing shows that Kronos, an open-source foundation model for financial time series, does not outperform the traditional Brownian motion model in predicting 5-minute Bitcoin price movements, based on a detailed out-of-sample analysis.

Over a two-week period, researchers compared Kronos-small, a 24.7 million parameter model trained on global exchange data, against a geometric Brownian motion baseline and market-implied probabilities in a simulated trading environment. The evaluation involved 497 historical BTC trades, reconstructed from market data, with models predicting the likelihood of price increases within five-minute windows.

The analysis employed multiple scoring metrics, including Brier score and log-loss, to assess forecast accuracy and confidence. Results showed that Kronos’s predictive performance was statistically indistinguishable from Brownian motion. On the full sample, Brownian slightly outperformed Kronos, while on the out-of-sample test set, differences were negligible, within the margin of statistical noise. Consequently, the study concludes that, in this context, the modern learned model does not provide a measurable edge over the classical stochastic assumption.

Polybot Week 3 — Kronos vs Brownian — Thorsten Meyer AI
KRONOS
● RESEARCH SERIES / MAY 2026
THORSTEN MEYER AI · POLYBOT · WEEK 3
POLYBOT · WEEK 3
KRONOS vs BROWNIAN
Research Series · Foundation Model vs Classical Baseline · 2026-05-17

Foundation model
vs Brownian motion.
Kronos on five-minute BTC.

A modern learned model just lost to math from 1900. On 497 paired trades. Stage 2 is not happening.
Polybot’s fair-value strategy uses a 1900s geometric Brownian model to price 5-minute BTC outcomes. The natural follow-up after two weeks of negative parametric results: would a modern learned model trained on millions of real candles do better? The credible candidate: Kronos — open-source MIT-licensed foundation model, 25,000+ GitHub stars, AAAI 2026, four sizes from 4M to 499M parameters, trained on candles from 45 global exchanges. Test design: 497 paired (FILL→SETTLE) trades, Brownian baseline reconstructed line-for-line, Kronos-small (24.7M params) sampled with 16 forecast paths, scored on Brier + log-loss + hypothetical P&L, chronologically split for out-of-sample discipline. On 249 out-of-sample trades: Brownian 0.188 Brier vs Kronos 0.189 Brier. Gap 0.0011. Statistically indistinguishable. Stage 2 is not happening. But the paradox is more interesting than the verdict: when used as a directional signal Kronos fires 28% less often and wins 60.7% vs Brownian’s 49.1% — slightly better trader on hypothetical P&L, even while systematically over-confident in the tails (predicts 2.4% chance → actual 20.4% win; predicts 84% → actual 69.6%). The negative result is the answer. The methodology is what gets published.
This is not financial advice. Nothing in this article should be used to inform real trading decisions. The bot trades simulated money. If you build something like it and run it with real funds, the most likely outcome — by a wide margin — is that you lose those funds. That holds whether you use a Brownian model, a 100-million-parameter foundation model, or any other forecaster.
497
Paired (FILL→SETTLE) trades
all BTC · 5-min Up/Down markets
0.0011
Out-of-sample Brier-score gap
249 trades · statistically indistinguishable
Kronos log-loss vs Brownian
signature of confident wrong predictions
+$538 / +$465
Hypothetical Kronos vs Brownian P&L
the paradox · 60.7% vs 49.1% win rates
POLYBOT WEEK 3· KRONOS-SMALL · 24.7M PARAMS· BROWNIAN BASELINE· 497 PAIRED TRADES · BTC· POLYMARKET 5-MIN UP/DOWN· BRIER 0.193 / 0.211 / 0.213· LOG-LOSS 0.567 / 0.604 / 1.080· OUT-OF-SAMPLE 0.188 vs 0.189· GAP 0.0011 · INDISTINGUISHABLE· STAGE 2 NOT HAPPENING· KRONOS BETTER TRADER · WORSE FORECASTER· 60.7% vs 49.1% WIN RATE· TAILS: 2.4% → 20.4% · 84% → 69.6%· POLYBOT MIT· KRONOS MIT· AAAI 2026 PAPER · 25K+ STARS· 11 MIN MAC M-SERIES · MPS BACKEND· 1,300 LINES OF PYTHON· RESEARCH_PIPELINE.MD PUBLIC· SAME GAUNTLET · DIFFERENT MODEL· POLYBOT WEEK 3· KRONOS-SMALL · 24.7M PARAMS· BROWNIAN BASELINE· 497 PAIRED TRADES · BTC· POLYMARKET 5-MIN UP/DOWN· BRIER 0.193 / 0.211 / 0.213· LOG-LOSS 0.567 / 0.604 / 1.080· OUT-OF-SAMPLE 0.188 vs 0.189· GAP 0.0011 · INDISTINGUISHABLE· STAGE 2 NOT HAPPENING· KRONOS BETTER TRADER · WORSE FORECASTER· 60.7% vs 49.1% WIN RATE· TAILS: 2.4% → 20.4% · 84% → 69.6%· POLYBOT MIT· KRONOS MIT· AAAI 2026 PAPER · 25K+ STARS· 11 MIN MAC M-SERIES · MPS BACKEND· 1,300 LINES OF PYTHON· RESEARCH_PIPELINE.MD PUBLIC· SAME GAUNTLET · DIFFERENT MODEL·
FIG. 01 — THE TEST PIPELINE
Five steps · for every paired (FILL → SETTLE) trade in the running session
~1,300 lines of Python · 11 minutes on Mac M-series with PyTorch MPS · methodology public, specific numbers local
1
Reconstruct OHLCV context of the 60 minutes leading up to fire-time. Pull from the bot’s local Binance recording where available; fall back to Binance’s public klines API otherwise. Cache to parquet so re-runs cost nothing.
2
Recompute the Brownian baseline in Python — a line-for-line port of the bot’s own fairValuePUp(spot, openPrice, secondsLeftFrac, windowVol) formula. Matches scipy.stats.norm.cdf to three decimal places.
3
Read off the market-implied probability from the FILL price — what Polymarket’s order book thought the side was worth at the moment of fire. The market’s view as a reference point.
4
Run Kronos-small (24.7M parameters) on the OHLCV context · sample 16 forecast paths to the window’s end · count the fraction in which the underlying closes above the open price. That fraction is Kronos’s predicted p(Up).
5
Record (p_brownian, p_market, p_kronos, actual_outcome, P&L). Score on Brier + log-loss + hypothetical P&L. Sort chronologically · split into first/second half · report on both halves separately.
The discipline that matters: if a model wins on the first half but ties or loses on the second, that’s the curve-fit-in-slow-motion pattern the previous two articles named, and it doesn’t count as edge. The whole pipeline is reproducible from docs/RESEARCH_PIPELINE.md. Any future candidate model gets a sibling directory in research//, reuses the same Brownian baseline, the same trade-log loader, the same OHLCV fetcher, the same metrics, the same out-of-sample split. Same gauntlet, different model, same discipline.
FIG. 02 — FULL-SAMPLE SCORING · 497 PAIRED TRADES
Three models · two probability-scoring metrics
Brier score and log-loss · the standard scoring rules for probability forecasts · lower is better
Model
Brier ↓
Log-loss ↓
BrownianGeometric Brownian motion · the 1900s baseline
0.193
0.567
Market-impliedPolymarket order book at FILL · reference
0.211
0.604
Kronos24.7M-param foundation model · 16 sampled forecast paths
0.213
1.080
Kronos’s log-loss is roughly twice Brownian’s — the signature of a model that makes confident, wrong predictions in the tails. Polymarket’s order book sits between the two, reasonably calibrated, slightly worse than the bot’s Brownian and slightly better than the foundation model. The 100-year-old math beat the 24.7M-parameter foundation model on both probability-scoring metrics.
FIG. 03 — OUT-OF-SAMPLE VERDICT · 249-TRADE TEST HALF
Chronologically-separated · never seen by tuning
The verdict the test was designed to deliver · noise band of repeated runs with different sampling seeds
Brownian · 249-trade test half
0.188
Brier score (out-of-sample)
lower is better
Kronos · 249-trade test half
0.189
Brier score (out-of-sample)
lower is better
The gap
0.0011
Statistically indistinguishable
inside the noise band
Kronos does not beat Brownian on a held-out chronologically-separated sample. So Stage 2 is not happening.
“Stage 2” was the planned next step: wiring Kronos into Polybot as a live strategy if Stage 1 produced a clear signal. The case is not earned by this data. For 5-minute BTC at the horizons the bot trades, the open Kronos-small checkpoint does not. Stop. The next candidate model — Chronos · TimesFM · Lag-Llama · a Kronos finetune on 5-min crypto · something else — goes through the same gauntlet. Most will fail it. That is the gauntlet doing its job.
FIG. 04 — THE PARADOX · BETTER TRADER vs WORSE FORECASTER
By operational standards Kronos wins · by probabilistic standards Kronos loses
The hypothetical-P&L counterfactual replays the same data through “what if Polybot fired on each model’s probability”
Operational view · Kronos as the better trader
Kronos fires less · wins more · nets slightly more.
Hypothetical fires
201
Brownian fires (reference)
279
Win rate (Kronos)
60.7%
Win rate (Brownian)
49.1%
Hypothetical net P&L (Kronos)
+$538
Hypothetical net P&L (Brownian)
+$465
Fires ~28% less often and wins more reliably when it does. If you use Kronos as a directional signal in a broader system that does its own sizing — closer to how TradingAgents uses analyst outputs — the directional accuracy might still be useful.
Probabilistic view · Kronos as the worse forecaster
Systematically over-confident in the tails.
Kronos predicts
2.4%
Trades actually win
20.4%
Kronos predicts
84%
Trades actually win
69.6%
Log-loss vs Brownian
~2× worse
Brier (full sample)
0.213 vs 0.193
If you are building a fully-probabilistic system where the probability feeds an expected-value calculation against the market’s implied price — which is what Polybot does — calibration is everything, and Kronos’s calibration is bad enough to disqualify it. It thinks it knows more than it does at both ends.
Both interpretations are honest. Neither earns the model a place in Polybot. One of them might earn it a place, later, in TradingAgents — as a 5th analyst voice that votes on direction without being trusted for calibrated odds. That experiment is not what this week tested; it is a separate hypothesis for a separate week.
FIG. 05 — WEEK FOUR · THREE POSSIBLE THREADS
Each is a separate article · the pattern across them is the same
Honest measurement · out-of-sample discipline · no rescue narratives when something doesn’t work
1
A second-tier candidate model · Amazon’s Chronos
Same general shape as Kronos · different training corpus · also open-source. Running it through the exact same gauntlet would say whether the negative result is specific to Kronos or generalises to learned models in this regime.
Generalisation test
2
Kronos with a finetune on 5-min crypto data
The Kronos repo ships a finetuning pipeline. Taking the open Kronos-base checkpoint, finetuning on the bot’s own recorded BTC tick history, re-testing. Isolates “is the pretrained distribution wrong for crypto?” from “is the architecture wrong for this horizon?”
Architecture vs distribution
3
A live-trading update on Polybot
The fleet has been running paper trades continuously across these three weeks. A fresh aggregate-P&L view, with the same calibration-style analysis applied to live performance rather than historical replay, is overdue.
Status reset
The contract is “same gauntlet, different model, same discipline.” Specific numbers stay local. Methodology is public on the repo’s docs/RESEARCH_PIPELINE.md. Publishing reproducible parameter recipes for strategies that might be marginally profitable encourages people to copy them with real money, and the prior on real-money outcomes when copying retail strategies is “they lose.” Publishing the methodology lets the next person test their own model honestly without inheriting any of mine.
By probabilistic standards · Kronos is a worse forecaster. By operational standards · Kronos is the better trader. Both interpretations are honest. Neither earns the model a place in Polybot. One of them might earn it a place, later, in TradingAgents.
Thorsten Meyer AI · Week 3 · Foundation Model vs Brownian Motion

Implications for AI-based Short-Term Trading

This finding challenges the assumption that advanced machine learning models automatically outperform traditional stochastic models in short-term market prediction. It suggests that, at least for 5-minute BTC forecasts, current foundation models like Kronos may not offer a trading advantage over simpler, well-understood models like Brownian motion. This has implications for developers and traders considering integrating such models into automated trading systems, emphasizing the need for rigorous validation before deployment.

Scalp Smart Hacks to Win Big in Forex Day Trading: Welcome to Scalp Smart, the comprehensive guide designed to transform your forex scalping journey from guesswork to consistent profits.

Scalp Smart Hacks to Win Big in Forex Day Trading: Welcome to Scalp Smart, the comprehensive guide designed to transform your forex scalping journey from guesswork to consistent profits.

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on Model Testing and Market Assumptions

Over recent years, AI and machine learning have been increasingly applied to financial markets, with the expectation that learned models can capture complex patterns beyond classical assumptions. Kronos, introduced as an open-source foundation model trained on extensive crypto market data, was designed to explore this potential. Previous experiments, including the author’s own two-week paper-trading bot, indicated that most ‘edges’ in short-term trading are mechanical artifacts rather than genuine predictive signals. The current study builds on this by directly comparing Kronos’s forecasts against a traditional Brownian motion model, which assumes independent, normally-distributed log-returns—a 100-year-old approximation still widely used as a baseline.

“The test results show that Kronos does not outperform Brownian motion in predicting 5-minute BTC price movements, at least in this out-of-sample setting.”

— Thorsten Meyer

Financial Literacy Flashcards for Kids & Teens | 108 Money & Finance Terms with Images, Definitions & Discussion Prompts | 3 Skill Levels (Beginner–Advanced) | Deluxe Set with Digital Activity Book

Financial Literacy Flashcards for Kids & Teens | 108 Money & Finance Terms with Images, Definitions & Discussion Prompts | 3 Skill Levels (Beginner–Advanced) | Deluxe Set with Digital Activity Book

📘 BONUS Digital Companion Activity Book: Includes a printable 108 page companion activity book with structured exercises and…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Model Performance and Market Conditions

It remains unclear whether different training regimes, larger models, or alternative market conditions could yield different results. Additionally, the study focused on a specific time horizon (5-minute windows) and market segment (Bitcoin), so the findings may not generalize across other assets, timeframes, or trading environments. The potential for learned models to outperform classical assumptions in different contexts remains an open question.

Crypto Wealth Without Wall Street: The Underdog Investor's Guide to Cryptocurrency, Bitcoin, DeFi, Yield Farming, and Creating Financial Freedom Without Banks

Crypto Wealth Without Wall Street: The Underdog Investor's Guide to Cryptocurrency, Bitcoin, DeFi, Yield Farming, and Creating Financial Freedom Without Banks

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Research and Practical Applications

Further research is needed to evaluate whether larger or differently trained models can outperform Brownian motion in short-term prediction. Developers may also explore integrating models with adaptive strategies or broader datasets. For traders and algorithm developers, the immediate implication is to maintain rigorous validation of any AI-based prediction tool before deployment, as current models do not show a clear advantage in this setting. Future studies may examine other assets, longer horizons, or more sophisticated architectures.

Market Data Analysis Using JMP

Market Data Analysis Using JMP

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

Does this mean AI models are useless for trading?

No, this study specifically compares Kronos to Brownian motion for short-term BTC prediction and finds no advantage. AI models may still be useful in other contexts or with different configurations.

Could larger or more complex models perform better?

This remains an open question. The current results do not rule out the possibility that bigger or differently trained models might outperform classical assumptions in future research.

Is this result specific to Bitcoin or applicable to other assets?

The study focused on Bitcoin at five-minute intervals. Results may differ for other assets, timeframes, or market conditions, and further testing is needed.

What does this mean for traders using AI tools?

Traders should be cautious and validate AI predictions rigorously, as current models do not necessarily offer a predictive edge over simple stochastic models in short-term crypto trading.

Source: ThorstenMeyerAI.com

You May Also Like

Segmentation for Test Environments: The Simple Way to Avoid Cross-Talk

Ineffective segmentation can lead to serious issues, but simple techniques can ensure your test environments stay isolated and secure—discover how.

Risk Matrices: Simple Visuals, Serious Insights

Ineffective hazard prioritization can jeopardize safety; discover how risk matrices provide simple visuals that deliver serious insights—and why they matter.

Building an AI Trading Bot — Week One: Why a 90 % Win Rate Can Still Lose Money

A week into testing an AI trading bot, high win rates do not guarantee profitability. The experiment reveals complexities in market pricing and strategy edge.

Threat Modeling for QA: Catch Security Flaws Early

Secure your software early by using threat modeling in QA to identify hidden vulnerabilities before they become costly to fix.