Skip to main content

Platform Mechanic and Server Exploits

Prohibited Trading Practices

Written by Oliver

Platform Gaps, Pricing Errors and Technical Glitches covers prices the platform gets wrong. This section covers everything else it can get wrong: leverage or margin that calculates incorrectly on a particular symbol, a spread that resets after rollover, a swap or commission that fails to apply, an order type that behaves differently from its exchange equivalent. These are defects, not market features. Trading a defect is not a strategy; it is a bug you have chosen to monetise rather than report.

What counts as a violation:

  • Known quirk exploitation: routing volume into a symbol, session, or order type because it is known to calculate leverage, margin, spread, or commission incorrectly.

  • Rollover and reset windows: concentrating activity in windows where spreads, swaps, or margin requirements are known to reset or misapply.

  • Order-type abuse: using an order type in a way that depends on simulated behaviour differing from exchange behaviour.

  • Probing: systematically testing symbols, sizes, sessions, or order types in order to locate an exploitable platform defect.

  • Continuing after discovery: continuing to trade a defect once you are aware of it, whether or not you found it deliberately.

What is allowed:

  • Trading a symbol with wide spreads or unusual margin because that is genuinely how the instrument behaves = ALLOWED

  • Trading the rollover or session-open window on a directional view = ALLOWED

  • Finding a defect and reporting it = ALLOWED, and reporting will never be held against you

  • Preferring a particular instrument or session because it suits your strategy = ALLOWED

Your responsibility:

The obligation in Platform Gaps, Pricing Errors and Technical Glitches applies here too. If the platform appears to be calculating something incorrectly, stop trading it and report it.

How this is assessed:

Known platform defects are instrumented as monitored events. Automated monitoring alerts when a single account hits an affected code path, symbol, or window at a frequency well outside baseline. Profit concentrated in a narrow set of symbols or time windows that correspond to a known defect is reviewed manually.

Did this answer your question?