PerpForge
Get started

Concept · Is it a real edge, or luck?

Sharpe Significance

The minimum number of trades needed for a measured Sharpe ratio to be statistically distinguishable from zero. Tells you how many trades it takes to prove "this strategy is better than random."

Sharpe Significance

The minimum number of trades needed for a measured Sharpe ratio to be statistically distinguishable from zero. Tells you how many trades it takes to prove "this strategy is better than random."

In plain English

If a strategy has a measured Sharpe ratio of 0.05, that could easily be random noise — a coin-flip strategy with zero true edge can produce small positive (or negative) Sharpe by luck. To be confident the Sharpe is real (i.e. not zero), you need enough trades that the measurement noise drops below the signal.

The stronger the Sharpe, the fewer trades you need. A truly amazing strategy can be validated quickly. A barely-edged strategy needs a huge sample.

Formula

For a per-trade Sharpe ratio S, the standard error is approximately:

SE(S) ≈ sqrt( (1 + 0.5 × S²) / N )

For S to be distinguishable from zero at 95% confidence, you need:

S > 1.96 × SE(S)
   → N ≈ (1.96 / S)²   (for small S)

Why it matters for this fleet

This formula is the most efficient way to ask "how many trades do I need?" without first running the backtest. Look at the observed Sharpe, plug in, get N.

True per-trade Sharpe N needed (95% confidence)
0.5 (extraordinary) ~16
0.3 (excellent) ~43
0.2 (good) ~96
0.1 (mediocre) ~385
0.05 (thin) ~1537
0.02 (very thin) ~9604

The decay is brutal: cutting Sharpe in half quadruples the trades needed. Thin edges are expensive to prove.

Examples from the live fleet

Here, "Sharpe" means per-trade Sharpe — the average per-trade return divided by the trade-to-trade volatility (how much the returns scatter around that average). A bigger Sharpe means a steadier edge.

  • id523 (EMA 21/50 · SOL · 1h · 2× · long): measured Sharpe 0.110, N=436. Required N at this Sharpe: ≈ (1.96 / 0.110)² ≈ 317. Actual 436 > 317 → sample passes. The edge is statistically distinguishable from zero. (It is still a poor strategy — it trailed simply holding SOL by 2013pp — but the edge itself clears the bar.)
  • id511 (EMA 21/50 · BTC · 1h · 2× · long): measured Sharpe 0.020, N=469. Required N: ≈ (1.96 / 0.020)² ≈ 9,213. Actual 469 ≪ 9,213 → sample fails badly. The measured Sharpe is far too thin for 469 trades to prove any edge.

The pattern: the difference between these two is not their trade count (436 vs 469 — almost the same). It is the strength of the edge. A Sharpe of 0.110 needs a few hundred trades to prove out; a Sharpe of 0.020 needs nearly ten thousand.

Caveat — the Sharpes here are genuinely small. Real trend-following Sharpes in this fleet sit in the 0.02–0.26 range. Thin edges are real, but they demand large samples to prove, which is exactly why most of the fleet cannot clear this bar.

Important nuance — annualized vs per-trade Sharpe

The simulator reports per-trade Sharpe, not annualized. Trading literature usually quotes annualized values. Conversion:

Sharpe_annual ≈ Sharpe_per_trade × sqrt(trades_per_year)

So a per-trade Sharpe of 0.1 on a 1h strategy generating 600 trades/year is 0.1 × sqrt(600) ≈ 2.45 annualized — institutional-grade. A per-trade Sharpe of 0.4 on a 1d strategy generating 30 trades/year is 0.4 × sqrt(30) ≈ 2.19 annualized — also excellent.

This is why thin per-trade Sharpe with high frequency can still be deployable; and high per-trade Sharpe with low frequency can still be statistically real.

Practical use

  1. Compute measured Sharpe from /api/analytics.
  2. Compute required N = (1.96 / Sharpe)².
  3. If actual N > required N → edge is statistically confirmed (not necessarily robust to regime change, but confirmed within this dataset).
  4. If actual N < required N → metric is suggestive but not proven; keep collecting data or pool family variants.

Related

Sources

  • wiki/qa-sessions/2026-05-17-session.md#q3 (first asked here)
  • Lo, A. W. (2002), "The Statistics of Sharpe Ratios", Financial Analysts Journal
  • /api/analytics

Related concepts

See it in a real result →

Put it to the test

Does your idea have a real edge, or just a big number?

Spawn your variant, run it on the same engine, and read the edge-significance verdict — before you risk real money.

Test your own idea — free →Free account, no card