TRADING RULES

Clear boundaries. Consistent treatment.

Use the simulation to test a trading process, not to exploit infrastructure errors.

Infrastructure abuse

Do not exploit stale quotes, manipulate API timestamps, bypass account ownership, share secret credentials, or deliberately attack the service. The server validates quotes and ignores client-supplied execution prices.

Algorithms are permitted

Python strategies, expert logic, and native copying across your own accounts are allowed. Rate limits and risk rules apply equally to manual and programmatic orders.

Minimum discretionary hold

The minimum is 5 seconds for a trader-requested close. Original protective stops and forced risk liquidations can exit sooner. Short-duration targets and recently modified stops are logged for contextual review.

Evidence before penalties

A rapid stop-out is not automatically micro-scalping. Review considers original protection, modifications, reason, duration, and repeated behavior. This build does not confiscate rewards automatically based on a short-duration flag.