Most prop trading firms publish their rules in language that sounds straightforward. Maximum drawdown of 10%. Maximum daily loss of 5%. Minimum 5 trading days. Profit target of 10%. 30-day time limit. Each rule taken individually is a clear constraint that any trader can verify against their backtest. Combined, they form a multi-dimensional decision problem that aggregate backtest statistics cannot solve.
The reason aggregate statistics cannot solve it is structural. A backtest produces one historical equity curve. The prop firm challenge will produce one future equity curve. The future curve will not be identical to the historical one — it will be drawn from a similar statistical distribution, but the specific sequence of trades and days will differ. The question is not whether the historical curve would have passed the challenge rules. The question is what fraction of plausible future curves, drawn from the same underlying distribution as the historical one, will pass.
This is a Monte Carlo problem in the strictest sense. And until now, no retail validation tool has solved it correctly. Most tools either ignore prop firm rules entirely, or apply them to the single historical equity curve and report a binary pass/fail that misrepresents the underlying probability. Some compute heuristic compatibility scores from aggregate statistics, which produce numbers that look authoritative but have no grounding in the actual mechanics of the challenge.
This is the problem the new Prop Firm Compatibility feature we are currently building for Edge Matrix is designed to solve. It is a full Monte Carlo simulation of the prop challenge itself — 1,000 independent simulated challenges, each running the strategy through its rules day by day, trade by trade, with every constraint checked continuously. The reported compatibility score is not an estimate. It is the actual pass rate from the simulation.
This article walks through the methodology of the feature in detail, written during its development phase, so traders and developers understand what the score will actually represent when the feature ships.
What the Engine Actually Does
The simulation works by building a pool of trading days from the backtest — every distinct calendar day on which the strategy generated trades — and then bootstrap-resampling that pool to construct simulated challenge sequences. Each simulated challenge consists of N trading days drawn with replacement from the day pool, where N is the user’s configured time limit (typically 30 days, capped at 180 for unlimited challenges).
For each of the 1,000 simulated challenges, the engine walks through the sampled days trade by trade. At every trade, the percentage return is applied to the running challenge balance — matching the way a percentage-risk-sizing EA actually scales when it is deployed on a different account size. At every step, all enabled rules are checked continuously: equity versus the maximum drawdown threshold, end-of-day P&L versus the daily loss threshold, current equity versus the profit target, and the count of distinct trading days versus the minimum requirement.
Each path produces one of five possible outcomes. PASSED means the strategy hit the profit target without violating any rule within the time limit. FAILED_DD means the maximum drawdown was breached at some point during the path. FAILED_DAILY means a single trading day’s loss exceeded the daily loss threshold. FAILED_TIMEOUT means the path ran out of days before either passing or failing on a rule. FAILED_MIN_DAYS means the path satisfied other rules but did not trade on enough distinct days to meet the minimum requirement.
After 1,000 paths complete, the compatibility score is the literal fraction of paths that ended in PASSED, multiplied by 100. A score of 73 means 730 of 1,000 simulated challenges passed. This is not an inference from aggregate metrics. It is the direct empirical pass rate from a structured simulation of the actual challenge mechanics.
The Two-Lens Approach: Challenge Pass Rate vs Long-Term Drawdown
A pure challenge pass rate would be misleading on its own. Many strategies are mathematically capable of passing a 30-day challenge while being unsuitable for funded account trading because their long-term drawdown profile exceeds the firm’s maximum drawdown rule when measured over a full year of trading. A strategy that passes the challenge in 73% of simulations but produces a worst-case 1-year drawdown of 22% on a firm with a 10% drawdown rule is not actually prop-firm compatible. The challenge is a 30-day filter. The funded account is a 1-year (or multi-year) commitment. The compatibility score has to reflect both.
The engine handles this with a second lens: a 1-year forward Monte Carlo projection of the strategy’s drawdown profile. This is a separate 1,000-path simulation over a 252-day (one trading year) horizon, computing the worst-case drawdown across the full set of paths. This worst-case drawdown is then compared against the firm’s maximum drawdown rule.
If the forward worst-case drawdown is within the maximum drawdown rule, the challenge pass rate stands as the final compatibility score. If the forward drawdown exceeds the rule, a severity multiplier is applied:
multiplier = 1 / (1 + 2.5 × excess)
Where excess is the fractional amount by which the forward drawdown exceeds the rule (a 22% forward drawdown against a 10% rule produces an excess of 1.2, multiplier of 0.25). The final score is the challenge pass rate multiplied by this severity factor.
A strategy that passes 73% of simulated challenges but has a forward worst-case drawdown of 22% against a 10% rule produces a final compatibility score of 73 × 0.25 = 18. The 73% pass rate is real — those simulations did pass the challenge within the 30-day window. The 18 final score reflects that the strategy’s structural drawdown risk makes it incompatible with the firm’s rules over a realistic funded account holding period, even though it can pass the initial filter.
This dual-lens approach is what the engine documentation calls “honest compatibility.” Strategies that look good on the 30-day challenge but blow up over a year of trading are not actually prop firm compatible, and the score reflects that.
Per-Rule Pass Rates: Where Specifically Does the Strategy Fail?
The aggregate compatibility score answers “what is the probability of passing the challenge?” The per-rule breakdown answers a different and equally important question: “which specific rule is the strategy most likely to fail?”
For each of the four core rules — maximum drawdown, daily loss limit, profit target, minimum trading days — the engine computes the fraction of paths that satisfied that rule independently of the other rules. A strategy might have a 73% overall pass rate while showing 95% satisfaction of the daily loss rule, 87% satisfaction of the drawdown rule, 81% satisfaction of the profit target rule, and 91% satisfaction of the minimum days rule. The overall pass rate is lower than any individual rule because the strategy needs to satisfy all of them simultaneously, but the breakdown reveals which rule is the binding constraint.
A strategy that satisfies the drawdown rule 99% of the time but the profit target only 72% of the time has a fundamentally different problem from a strategy that satisfies the profit target 95% of the time but the drawdown only 76% of the time. The first is too cautious — it does not generate enough return to hit the target reliably. The second is too aggressive — it generates enough return but takes too much risk along the way. The same overall compatibility score in both cases would imply they need similar fixes. The per-rule breakdown reveals that they need opposite fixes.
The failure breakdown goes further. Among the failed paths, the engine reports the percentage that failed by drawdown breach, by daily loss breach, by timeout, and by minimum days not being reached. A strategy where 80% of failures are timeouts is a strategy that does not have a risk problem — it has a return problem. It is not blowing up the account; it is failing to make progress fast enough. A strategy where 80% of failures are drawdown breaches has the opposite issue. The fix paths are completely different and the failure breakdown points directly at which fix matters.
The Killer Trades Analysis
The simulation operates on percentage returns applied to the challenge balance, which captures the typical case where the EA uses percentage risk sizing. But there is a specific failure mode that this method does not directly address: individual outsized losing trades that would have breached the daily loss limit regardless of the percentage scaling.
A strategy might pass a Monte Carlo challenge simulation in aggregate while still containing specific historical trades that, when scaled to the challenge account size, would have violated the daily loss rule. These “killer trades” are not a probability question — they are a deterministic fact of the historical record. The engine identifies them by scanning the historical trade log for trades whose magnitude exceeds the daily loss threshold when scaled to the challenge balance, and reports them separately from the Monte Carlo results.
This matters because the Monte Carlo simulation may show a 75% pass rate while the historical record contains, say, 8 specific trades that would have ended the challenge instantly if they had occurred during the challenge period. The compatibility score reflects the average probability across plausible challenge sequences. The killer trades report reveals the specific catastrophic events that the historical record contains, which the average obscures. A strategy with a 75% compatibility score and 8 killer trades in its history is a different proposition from a strategy with a 75% score and zero killer trades.
The Integrity Gate
A critical aspect of the Prop Firm Compatibility design is that the score does not exist in isolation from the broader Edge Matrix integrity checks. Before the simulation is run, the engine queries the Monte Carlo robustness analysis from the main Edge Matrix pipeline. If that analysis flagged the backtest as failing integrity checks — too few trades, signs of look-ahead bias, statistically implausible win rate, or other red flags — the compatibility score is suspended.
This is not a soft warning. The score is replaced with an explicit “suspended due to integrity issues” message and no compatibility number is reported. The reasoning is direct: if the underlying backtest data has integrity problems, every downstream analysis is contaminated. Reporting a 73% compatibility score on a backtest that contains look-ahead bias would be technically a true number from the simulation but a misleading one in context, because the simulation is sampling from a corrupted distribution. The engine refuses to report scores under those conditions.
This design choice is rare in retail validation tooling. Most tools will produce a score regardless of input quality, leaving the user to interpret whether the score is meaningful. Edge Matrix takes the opposite position: a number that cannot be trusted is more harmful than no number at all. The integrity gate exists specifically to prevent the compatibility score from being used as authoritative evidence on a backtest that does not warrant authoritative analysis.
Confidence Intervals: Acknowledging the Sampling Uncertainty
Even when the simulation is valid and the score is reportable, the score itself is an estimate from 1,000 samples. Running the simulation again would produce a slightly different number — perhaps 71 instead of 73, perhaps 75 instead of 73. The engine reports this Monte Carlo sampling uncertainty as a 95% confidence interval, computed by bootstrap resampling the 1,000 path outcomes 500 times.
A compatibility score of 73 might be reported with a 95% confidence interval of 70 to 76. This means: if the simulation were run many times, 95% of the resulting scores would fall between 70 and 76. The point estimate is 73. The uncertainty is plus or minus 3 percentage points from sampling noise alone.
The confidence interval is wider when the score is closer to 50% — which makes sense, because the binary pass/fail outcome has maximum variance when the underlying probability is near 50%. A score of 95% might have a confidence interval of 94 to 96 (very narrow), while a score of 50% might have an interval of 47 to 53 (wider). Reporting the interval allows the trader to distinguish between “high confidence the score is approximately X” and “the score is in the neighborhood of X but could vary by several points.”
This is a meaningful distinction. A strategy with a 56% compatibility score and a 95% confidence interval of 52 to 60 is meaningfully different from one with 78% and an interval of 76 to 80. Both are positive scores. The first is in a zone of genuine uncertainty about whether the strategy is likely to pass. The second is in a zone of confident expectation that it will. Aggregate scores without intervals conflate these scenarios.
Presets vs Custom Rules
The feature includes presets for major prop firms — FTMO 2-Step, FundedNext Stellar, The5ers High Stakes — with rule values matching those firms’ published challenge parameters. Selecting a preset configures the simulation with that firm’s specific drawdown rules, daily loss limits, profit targets, time limits, and minimum trading day requirements.
The custom mode allows the user to input any rule combination. This matters because prop firm rules change frequently, new firms emerge, and the published rules of any specific firm may not match what is actually enforced for any specific challenge. A trader evaluating a strategy for a firm not in the preset list, or for a challenge with non-standard rules, can configure the simulation to match the actual constraints they will face.
The simulation accepts the rules as parameters and runs the same underlying engine regardless of which preset or custom configuration is selected. The methodology does not change. Only the constraints applied at each step change. This means the compatibility score is meaningful for any rule combination, not just the major firms that the presets cover.
What This Tool Is Not
The Prop Firm Compatibility feature is rigorous in what it does. It is also explicit about what it does not do.
It does not predict whether a specific instance of the trader’s challenge will pass. The 73% compatibility score means that 73% of plausible challenge sequences pass — the specific challenge the trader runs may be one of those 73% or one of the 27%. The score is a probability across the distribution of possible outcomes, not a forecast of any individual outcome.
It does not account for execution differences between the backtest environment and the live prop firm environment. Spreads may be wider on the prop firm’s broker. Slippage may be higher. News event handling may differ. Trade execution timing may not match the historical record. These execution differences are not captured by the simulation, which operates on the historical trade data as recorded in the backtest.
It does not validate the strategy’s underlying edge. A strategy with a 95% compatibility score on a poorly validated backtest is still trading on a poorly validated backtest. The Compatibility Score answers the question “given this historical performance, what is the probability of passing the challenge?” It does not answer “is this historical performance trustworthy?” That is what the rest of the Edge Matrix Score’s 18 tests address. The Compatibility Score is best used after the strategy has passed the underlying validation tests, not as a substitute for them.
It does not constitute financial or trading advice. Whether to attempt a prop firm challenge with any specific strategy is a decision the trader must make based on their own assessment of the strategy, the firm, the costs, and their own risk tolerance. The Compatibility Score is one input into that decision, not a recommendation about whether to proceed.
How This Changes the Validation Workflow for Prop Traders
The standard pre-challenge workflow for a prop trader evaluating an EA has historically involved several manual steps: examine the backtest for obvious red flags, compute or estimate the historical maximum drawdown relative to the firm’s rule, look at the win rate and profit factor to assess whether the profit target seems achievable, and make a judgment call about whether to commit the challenge fee.
The Prop Firm Compatibility feature replaces the judgment call with a calibrated probability. Instead of “this looks like it should work, the drawdown is 7% so it should pass FTMO’s 10% rule,” the trader gets “the simulation produces a 73% pass rate with a 95% confidence interval of 70 to 76, the binding constraint is the profit target (81% individual satisfaction rate), and the 1-year forward worst-case drawdown of 9.2% is within the firm’s 10% rule, so the full score is not penalized.”
This level of specificity changes the decision. A trader who learns that 73% of simulations pass might still attempt the challenge — the expected value of a $50 challenge fee for a 73% chance of a funded account is favorable if the funded account is valuable enough. A trader who learns that only 22% of simulations pass has been given concrete information that the strategy is unlikely to pass and the challenge fee is more likely than not to be lost. Both decisions are now informed rather than guessed.
The Compatibility Score is also useful in the opposite direction: for traders who have a strategy and want to identify which prop firm rules it is most compatible with. Running the simulation against multiple presets — FTMO, FundedNext, The5ers, and custom configurations of other firms — reveals which firms’ specific rule structures are best matched to the strategy’s behavior. A strategy might score 78% for FTMO 2-Step but only 41% for a firm with stricter daily loss limits, indicating that the strategy’s risk profile is acceptable on a per-position basis but produces some difficult days that would breach tighter daily limits.
Why This Is the Hardest Edge Matrix Feature to Build Correctly
The complexity of this feature is not in the individual computations. Each component — the Monte Carlo sampling, the rule checking, the forward projection — is straightforward statistical work. The complexity is in the integration: ensuring that the simulation methodology is mathematically defensible, that the score communicates honest probability rather than false precision, that the integrity gates prevent misleading outputs on bad data, and that the rule structures of different prop firms are correctly modeled.
The decision to apply the forward drawdown multiplier was a long deliberation. A simpler design would have reported the raw challenge pass rate and let the trader decide separately whether the long-term drawdown risk was acceptable. The two-lens approach was chosen because the raw pass rate alone misleads traders into thinking a strategy is compatible when it would be incompatible over a realistic funded account period. The multiplier is the engine’s honest correction for this gap between the challenge mechanics and the actual stakes of a funded account.
The choice to use percentage-return scaling rather than fixed-lot scaling as the default reflects how serious algorithmic traders actually run EAs. Strategies that use fixed lot sizing on different account sizes are exposed to drawdown risk that scales inversely with account size — a behavior that is generally avoided in production deployments. The default reflects best practice. The fixed-lot scaling option exists for strategies that genuinely do not scale with balance, but it produces different — and usually less favorable — results.
The integrity gate’s decision to suspend the score rather than report it with caveats is a position on user experience: a score with caveats is still a score, and users interpret scores as actionable information. A suspended score with an explicit explanation is harder to misuse. The cost is that the feature appears “less complete” when integrity issues are present. The benefit is that traders cannot accidentally use compatibility numbers from corrupted backtests as evidence in their decision-making.
The Prop Firm Compatibility feature is currently in development at ErgodicLabs and will be added to Edge Matrix as part of an upcoming release. When live, it will be the first retail validation tool to run actual Monte Carlo simulation of prop firm challenges with rule-by-rule compliance breakdown, and the first to combine challenge pass rate with long-term drawdown projection in a single integrated score. The feature will work on any MT4, MT5, or cTrader backtest that has passed the underlying integrity checks.
Edge Matrix is available at ergodiclabs.co with a 7-day free trial. The free Backtest Graph Rebuilder at ergodiclabs.co/free-backtest-graph-builder provides visual backtest reconstruction with no account required. Subscribers will receive the Prop Firm Compatibility feature automatically when it launches.