Prop Firm Challenge Tips

Declared news-window checker

Join supplied execution events to literal instrument/action scopes and explicit UTC boundary operators.

Added 14 October 2026

Three explicit scope dimensions

An event matches only when its instrument, action and timestamp meet the entered window. None is inferred from a firm name. Fictional X1/X2 carry no real-market mapping. Open, close, stop-fill, target-fill and cancellation are separate actions. Holding is not an execution input here. The checker therefore cannot reconstruct a position, residual quantity or holding permission. Its result locates supplied events under the stated scope. A comprehensive account record would need additional observations and accepted applicability. A precise match is useful only when it remains attached to the source and interpretation actually entered.

Two endpoint operators

Start and end inclusion are independent booleans. An inclusive endpoint admits an event exactly at that timestamp; an exclusive endpoint does not. A zero-duration window matches its exact time only when both operators are inclusive. The exclusive-end sample changes E6's classification without changing E6. This is a teaching convention, not a statement of a programme's tolerance. Whole-second records cannot resolve finer ordering. A real boundary question needs authoritative precision and accepted wording. Do not round to a favorable side or treat a format-valid timestamp as proof of the source clock's accuracy.

Literal identities and action populations

Window instrument lists and action lists contain unique supported identities. A USD calendar label is not automatically mapped to every affected symbol, and a futures alias is not automatically mapped to another expiry. Mapping requires its own evidence. The second-instrument variant explicitly includes X2; the cancellation variant explicitly includes cancel. Their results demonstrate scope changes, not a named firm policy. A cancellation event does not prove a pending order was absent unless the authoritative record establishes its meaning. Preserve request, acknowledgement and fill stages outside the public checker when the actual question depends on them.

Overlaps preserve each window

An event may match several declared windows. In the overlap case E3 retains W1 and W2, giving four window matches across three matched event identities. Those totals answer different questions. Neither is a count of completed trades, account violations or participants. Each window should keep its source identity so overlaps are not collapsed into an ambiguous verdict. Output follows input order but infers no priority or legal hierarchy. Another programme term may be authoritative or relevant; the arithmetic cannot decide that relationship. A literal join remains separate from the administrative account process.

Observation resolution remains bounded

UTC timestamps contain whole seconds and valid dates from 2000 through 2099. Execution rows are ordered, with tied times retained in input order. Event and window identities are unique within their populations. Windows cannot end before they start. These constraints reject contradictory records but do not authenticate the clock or detect missing events. The tool does not fetch calendars or reconstruct intervening activity. A detailed trace can still be a selected population. Unobserved executions remain null, not zero. Keep precision, source timezone and the coverage period with actual records when investigating an account question.

Matches do not grant permission

A matched event is an input classification; an unmatched event is not approved. A different restriction, wrong card, missing revision or unsupported mapping can still matter. The programme owns its administrative decision, while this publication owns the authored explanation and join implementation. Permissions, account approval, payout eligibility, continuous monitoring and strategy validation remain null. No protective order, native exit or size is changed. The supplied input set and actual product card should stay separate at review. Valid arithmetic cannot replace the accepted rule or establish what happened on an account the publication has not observed.

Preparation records