forex-scalping.com

I will not turn Exness anecdotes into a verdict. I will tell you what I verify myself when anyone cites a story.

Verify: account type and entity, the exact time of the fill in server time, whether news was live, whether the order was market or stop, and whether the deals tab shows the slip you claim. Screenshots without those fields are campfire talk. I have seen both fine fills and ugly ones on multiple brands; the useful question is whether your log, on your hours, is acceptable for your stop size.

A good example: someone posted a 4-pip slip on a stop as proof the broker was bad. When I asked for the time, it was 13:30:01 London on NFP day. That is not an execution story, that is a news story, and any broker would have shown something similar.

The opposite also happens. Quiet 10:00 London, normal spread, and a stop fills two pips worse. That one deserves a ticket to support and a line in your own scorecard.

Anecdotes start research. They do not finish it. Finish it with your own sample or do not size up.

Anecdotes about the brand in the title only start a checklist for me. I verify entity and account type first, then the fill time in server time, whether news was live, market versus stop, and whether the deals tab shows the slip claimed.

Screenshots without those fields stay campfire talk. A four pip stop slip at 13:30:01 London on a payroll morning is a news story on any book; the same slip at quiet 10:00 London with normal spread is a ticket to support and a line in my scorecard.

I keep my own sample by hour and order type before I change size. Ugly fills clustered only around releases tell a different story than ugly fills on calm mid morning stops.

Support replies go in the same folder as the deals export. Memory of a bad week without the fields is how I used to blame the path for my own timing.

Anecdotes finish nothing on their own. What fields do you demand before an execution story changes your size or your broker shortlist?

LondonScalper, entity drift under the same brand is the verification step I now run before any anecdote changes my size. Two entities can share a logo and still differ on average stop slip in the same London hour, so I match the story's account entity to mine before I care about the screenshot.

I keep a short support ticket template with five fields: server time of the deal, order type, symbol, intended versus fill, and whether a Tier-1 print was inside fifteen minutes. Stories that cannot fill those fields never reach the scorecard.

Weekend gap slips get their own tag, separate from weekday news slips. Mixing them made one book look worse than it was on calm Tuesdays and better than it was on Sunday opens.

When I escalate, the deals export and the template go in the same mail. Memory of a bad week without fields still tries to sneak in; the template blocks it before the send.

Size changes wait for thirty comparable fills in the same hour bucket. One viral anecdote never moves the lot step on my card.

Which field do counterparties omit most often when they send you an execution complaint?