Skip to content

Challenge and risk engine development

The challenge engine decides whether a trader passes, fails or gets funded. It has to apply the same rules to every account, react fast enough to stop a breach, and leave a record that explains each decision.

What tends to go wrong

  • A daily-loss or drawdown floor can be measured on balance, on equity, or from a snapshot at a reset time. Small differences in that definition produce false breaches, or missed ones.
  • Programs change. When a firm applies new rules to accounts that were sold under the old ones, traders notice, and some firms have faced public backlash for it.
  • Checking every account on a timer gets slower as the number of accounts grows, and a breach found late can't be taken back.
  • When a trader disputes a breach, support has to show which price and which rule triggered it.

What I've built

Rules pinned to the account

In NEXETRO the rules are attached to an account when it's created, so editing a program doesn't change the rules for traders already in it.

See it in the case study: Rules pinned to the account

Two-pass breach detection

A live pass reacts as soon as a floor is touched and, until the breach is confirmed, refuses fills that would add exposure. A settled pass judges from the market archive, including accounts the live pass couldn't price.

See it in the case study: Two-pass breach detection

Challenge lifecycle

Profit targets, drawdown and daily-loss floors, consistency rules, and automatic progression from evaluation phases to a funded account.

See it in the case study: Challenge lifecycle

A detector that keeps up

I profiled the breach detector when it used too much CPU, then decoded market data once per cycle, skipped instruments with nothing new and cached the pinned rules.

See it in the case study: A detector that keeps up

What I can take on

  • Design or rebuild a rule engine for your programs: profit targets, daily loss, static or trailing drawdown, consistency rules and phase progression.
  • Write the rules down as a specification with test cases for the edge cases: resets across time zones, a price gap through a floor, a fill and a breach at the same moment.
  • Review an existing engine's breach logic against the rules your site publishes.
  • Add a breach record that support staff can show to a trader.

What I haven't done yet

I haven't shipped an integration with MetaTrader 5 (Manager API), cTrader, DXtrade or Match-Trader. NEXETRO runs its own execution and rule engine on exchange market data from Hyperliquid, so its risk logic doesn't depend on a platform licence. If your firm runs on one of those platforms, I'd scope the integration against its API documentation and say so in the estimate.

Related work

All prop firm development work

Building or fixing part of a prop firm?

Tell me which platform or market data you use, roughly how many accounts you run, and what needs to change. I'll reply with questions or a first outline of the work.

Get in touch