Hedging bans and multi-pair scalp books on prop accounts

[PTScalper]

This snippet uses a ConcurrentDictionary to guarantee thread safety, which is critical if you are aggregating exposures asynchronously inside a .NET background service or a multi-threaded tick event handler in a cTrader cBot.

The logic natively isolates the base and quote legs:

Base Leg (baseDeltaNative): Straightforward volume addition or subtraction. If you buy 1 lot of EURUSD, you hold +100,000 EUR.

Quote Leg (quoteDeltaNative): Calculated by multiplying the volume by the current exchange price, representing the liability used to fund the trade. It is also directly adjusted by the FloatingPnLNative, because unrealized profits or losses physically accrue in the quote currency.

[PTScalper]

If you have overlapping positions (e.g., Long EURUSD and Long USDCHF), the loop safely accumulates the conflicting USD quote and base values inside the dictionary. A heavily hedged USD exposure will naturally net out to a value close to zero in matrix["USD"].

To finalize the tracking for a hard exposure limit, you would inject an IRateProvider interface into this class. That provider would take the resulting dictionary (e.g., EUR: 100000, JPY: -15000000) and multiply each currency's net total by its live exchange rate against your base account currency, producing a single, consolidated risk value.

[Shadow Trader]

Two accounts can show the same symbol, the same leverage and the same spread, and still behave differently where scalpers feel it most. The difference is how positions are stored.

On a hedging account, each order becomes its own position with its own ticket, stop and target. Buy twice and there are two tickets. Sell while long and a separate short appears next to them.

On a netting account, orders on a symbol merge into one position per symbol. Buy twice and the volume adds up with an averaged entry price. Sell part of it and the position shrinks. Sell more than the position size and it flips direction.

Why this matters for scalpers:

- Stops and targets belong to the whole position, so a second entry with a different target can overwrite the levels of the first.
- Scaling out in pieces shifts the average price, which makes the real breakeven harder to track by eye.
- An EA written for one-ticket-per-trade logic can misbehave on netting, because the ticket it is tracking may vanish or change volume.
- Grid or multi-entry styles that depend on independent positions simply do not map across.

Commission and swap are also recorded differently, so reading the statement feels different too.

Neither type is better. Netting is cleaner for a single-direction scalper who thinks in net exposure. Hedging suits independent setups on the same pair. The trouble starts when one is assumed to behave like the other.

Has a strategy ever worked fine on one account type and fallen apart on the other, and what turned out to be the cause?

[FXS Prop Desk]

Thanks for the honest view from the spot side, PTScalper. Portfolio-level exposure is the useful takeaway even outside prop rules. Holding a long EURUSD and a short EURGBP, for example, is not a hedge at all, it is mostly a short GBP position. A simple net exposure table by currency, updated before each new trade, shows that immediately. For anyone running several pairs on a prop account, it also makes it easier to spot positions that a firm might treat as a hedge, even when they were not meant as one.