Independent Validation · Research Desk Engine

Do the numbers hold up on the real market?

Before onboarding a single club team, three questions had to be answered with evidence, not assertion: are the Desk's backtest numbers true, does its overfitting-detection work, and does an in-sample winner survive on a future it never saw? This is the audit — run on real BTC and ETH, and on candles fetched the day it was written.

Engine commit f4778b5 Data 13,152 h BTC/ETH (Jun 2024–Nov 2025) + 5,467 h fetched live Costs 0.15%/leg, net throughout Method pre-registered · deterministic
Part 1 — Correctness
Faithful

A from-scratch reimplementation matches the engine to 0.000000 percentage points across five rules.

Part 2 — Rigor
Honest

The overfitting gate flags a 10-of-10 in-sample winner as luck: 2.8/10 out of sample.

Part 3 — Forward test
Confirmed

A frozen +27% in-sample pick lost −7.6% on unseen data — exactly as warned.

PART 1

The engine computes what it claims

A backtest tool is only worth trusting if its arithmetic is exactly right. The first test ignores the Desk's own code entirely: a second backtester was written from scratch in plain Python — separate entry logic, separate P&L, separate cost model — and pointed at the same 13,152 real BTC hourly candles. If the two disagree by a cent, the engine is suspect.

Dip-buyer rule · net return after costs · real BTC 1h (Jun 2024 – Nov 2025)n = 13,152 candles
Rule (drop% / lookback / hold)Engine netIndependent netDifferenceTrades
1% / 20 / 30−35.6702%−35.6702%0.0000247 = 247match
2% / 30 / 40−46.6069%−46.6069%0.0000133 = 133match
3% / 50 / 30−52.6604%−52.6604%0.0000127 = 127match
5% / 20 / 60+9.6849%+9.6849%0.000027 = 27match
1% / 10 / 20−116.3858%−116.3858%0.0000310 = 310match

The worst disagreement across all five rules was 0.000000 percentage points, with identical trade counts. Reconciling the two required pinning down three exact behaviours the independent version had to replicate — entries priced at the candle close, exits exactly hold candles later, one position at a time with re-entry blocked until the candle after an exit, and any position still open at the window's end force-closed on the final candle. Once those matched the engine's, the numbers were bit-identical. The Desk reports precisely what it does.

PART 2

The honesty machinery catches a false edge

A correct engine can still flatter a bad idea if it only ever reports one number. The Desk's real job for a training team is the opposite: to say “this looked good, but it won't repeat.” Three of its rigor tools were run on real data to check they do exactly that.

Walk-forward — was the edge consistent, or only on average?

Each rule is re-run on the earlier 60% and the later 40% of the window separately, and its beat-the-random-baselines score is compared across the two halves. A number that is strong early and weak late is flagged as overfit.

Same rule, two halves of the window · beat-K of 10 random baselines · net
MarketRuleFull-window netBuy & holdEarlier halfLater halfVerdict
BTC 1hmomentum 0.5/20/40−12.14%+33.21%1/109/10held up
BTC 1hdip 2.0/30/30−33.18%+33.21%5/102/10neutral
ETH 1hmomentum 0.5/20/40−62.98%−20.80%7/102/10overfit
ETH 1hdip 2.0/30/30−95.36%−20.80%4/102/10neutral

The ETH momentum rule beat 7 of 10 baselines early and only 2 of 10 late — correctly labelled overfit. No rule here beat a passive buy-and-hold over the full window; the Desk says so plainly rather than cherry-picking the flattering half.

The 36-variant sweep — does the best-of-many survive?

This is the trap every backtester falls into: try 36 variations, keep the best, and be fooled by the luckiest one. The Desk's haircut takes that same in-sample winner and re-scores it out of sample against the no-skill line (a coin flip beats ~5 of 10 baselines by chance).

10.0 / 10
Best of 36, in sample — the inflated number
2.8 / 10
Same pick, out of sample — the honest number
5.0 / 10
No-skill baseline (pure luck)
Did not survive
Below chance out of sample → overfitting, not signal

Verdict, in the Desk's own words

“You compared 36 variations. The best in the earlier half beat 10 of 10 baselines — but picked from 36, that number is inflated by luck. Tested out-of-sample, that same pick beat 2.8 of 10 — about the ~5 of 10 you'd get by luck. The edge did not survive: it's consistent with overfitting 36 tries, not a real signal.”

Bootstrap & regime — is it luck, and where did it work?

Two more read-outs on a 247-trade dip-buyer. A Monte-Carlo bootstrap resamples the actual trades 1,000 times to build a confidence band; a regime split attributes the result to the market state at each entry — and, as a correctness check on itself, the three buckets must sum back to the headline exactly.

Bootstrap · 1,000 resamples

  • P5   −110.13%
  • Median  −36.29%
  • P95   +37.31%
  • Prob. profit  22%
  • A band that spans zero → the result leans on a handful of trades. Fragile.

Regime split · reconciles to headline

  • Up markets  54 tr  +17.51%
  • Down markets  123 tr  −38.06%
  • Flat markets  70 tr  −15.12%
  • Σ = −35.67%  =  headline −35.67%
  • Δ 0.0000 — the attribution is exact, not approximate.
PART 3

The final test: a future the engine never saw

In-sample and walk-forward tests still touch data the rule was chosen on. The only fully honest check is out-of-time. So the best-of-36 dip-buyer was frozen on the seen data, and then — with its parameters locked — measured on 5,467 fresh BTC candles fetched live from Binance for the window right after the training data ends. No re-tuning, no second look.

Frozen rule · drop 4% / lookback 5 / hold 60 · pre-registered before seeing forward data
MeasurementSeen data (Jun 2024–Nov 2025)Unseen future (Dec 2025–Jul 2026)
Selection rankbest of 36 — beat 10/10— (frozen, not re-picked)
Net return after costs+27.05%−7.62%
Buy & hold, same window−26.54%
Beat-K vs 10 random10/105/10
Trades taken9
Walk-forward on forward data5/10 → 2/10 (neutral)

The rule that looked like a +27% winner in the backtest lost −7.6% on the future it never trained on, and matched only 5 of 10 random baselines — the coin-flip line. It “beat” buy-and-hold's −26.5% only by sitting in cash while BTC fell (9 trades in seven months), not by any demonstrated skill. That is not a disappointment — it is the whole point.

Why this is the system working

Part 2's haircut predicted this rule would not survive. Part 3, on data that did not exist when the rule was chosen, confirmed it. The Desk's warning and reality agree. A team using this tool is told the truth before risking capital — which is exactly what a training instrument for finding an edge must do first: reliably tell you when you have not found one.

What this validates — and what it doesn't

What the evidence establishes

  • The engine's returns, trade counts and costs are exact — reproduced to zero error by independent code.
  • Its overfitting, walk-forward, bootstrap and regime tools flag false edges honestly on real data.
  • An in-sample winner, frozen and forward-tested on unseen candles, behaved exactly as the tools warned.
  • It is a sound instrument for teaching teams to separate signal from noise, net of real trading costs.

What it deliberately does not claim

  • That the Desk finds a guaranteed edge — none of the rules tested here beat the market out of sample.
  • That any specific strategy shown is profitable to trade. Most simple rules lose after costs; that is honest, not a defect.
  • That crypto results transfer unchanged to NEPSE or other markets — each needs its own validation.
  • That backtest history predicts the future. The forward test exists precisely because it doesn't.