\n| Latency-induced artifact<\/td>\n | Broker A’s feed received a market event faster. Apparent discrepancy = price move, not LP difference<\/td>\n | 30ms to 150ms<\/td>\n | Broker B has already updated by fill time — loss or requote<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nThe contamination ratio problem<\/h3>\nWithout filtering, the ratio of latency-induced signals to genuine LP discrepancy signals in a typical two-broker setup is 60–80% latency artifacts. Market events — price ticks, economic releases, liquidity shifts — happen continuously and each creates a transient latency-induced discrepancy as the faster broker’s feed updates first. The ratio depends heavily on the feed speed differential between the two brokers: a broker pair where one feed is consistently 100ms faster than the other generates far more artifacts than a pair within 10ms of each other.<\/p>\n Why latency-induced signals create toxic order flow<\/h2>\nExecuting on latency artifacts is unprofitable at the individual trade level. But the problem extends further — it creates a specific order flow pattern that brokers classify as technically toxic.<\/p>\n \n \n PATTERN 1<\/div>\n Orders at price move events<\/h3>\nLatency-induced signals fire precisely when a price event occurs — because that is when the fast broker’s feed updates while the slow broker’s has not. Unfiltered hedge arb places a disproportionate share of orders at the exact moments of price movement events. Broker risk systems that correlate order timestamps with price event timestamps identify this concentration as technical flow.<\/p>\n<\/p><\/div>\n \n PATTERN 2<\/div>\n High adverse selection rate<\/h3>\nLatency-induced trades consistently fill at unfavourable prices relative to the market a few hundred milliseconds later. Broker risk systems track short-term price trajectory after each fill. A high percentage of fills immediately followed by adverse price movement — the signature of orders arriving at the moment the market moved against the fill direction — flags the account for adverse selection review.<\/p>\n<\/p><\/div>\n \n PATTERN 3<\/div>\n P&L inversely correlated with volatility<\/h3>\nA system executing on latency artifacts is profitable during low-volatility periods (genuine LP discrepancies dominate) and unprofitable during high-volatility periods (latency artifacts multiply). This inverse correlation between P&L and volatility — inconsistent with legitimate technical trading — is a recognisable toxic flow signature.<\/p>\n<\/p><\/div>\n \n PATTERN 4<\/div>\n Asymmetric hold-time distribution<\/h3>\nWhen a latency-induced trade fills at the wrong price, the system exits within seconds. This pattern — profitable trades holding longer, losing trades closing fast — produces an asymmetric hold-time distribution that risk systems flag as automated technical exploitation.<\/p>\n<\/p><\/div>\n<\/div>\n \n The classification consequence<\/h3>\nOnce classified as toxic flow, the account receives degraded execution — requotes, spread widening, or internal routing to the broker’s own book. This also degrades the profitable genuine LP discrepancy trades.<\/strong> The filter problem is not just about individual trade profitability — it determines whether the account remains viable for arbitrage at all.<\/p>\n<\/div>\nSimple filter: difference-to-open threshold<\/h2>\n\n The simplest filter is a minimum price discrepancy threshold — difference-to-open — below which no order is placed.<\/strong> Latency-induced discrepancies tend to be smaller on average than genuine LP discrepancies: feed latency artifacts reflect only the speed differential between two feeds receiving the same event, while genuine LP discrepancies reflect actual LP-level pricing differences which can be larger and more persistent. Setting a minimum threshold cuts the smaller latency-induced signals while retaining the larger genuine ones.<\/p>\n<\/div>\nCalibrating the threshold<\/h3>\n\n\n\n| Step<\/th>\n | Action<\/th>\n | Output<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Step 1<\/td>\n | Run in monitoring-only mode for 5–10 trading days. Log every detected discrepancy with: timestamp, magnitude (pips), duration before collapse, and price movement in the 200ms following detection.<\/td>\n | Raw signal dataset<\/td>\n<\/tr>\n | \n| Step 2<\/td>\n | Post-hoc classify each signal: genuine (persists over 150ms, reference feed quiescent) or latency-induced (collapses under 100ms, preceded by directional price event).<\/td>\n | Classified dataset<\/td>\n<\/tr>\n | \n| Step 3<\/td>\n | Plot magnitude distribution of genuine vs latency signals. Find the threshold at which 80%+ of signals above it are genuine LP discrepancies.<\/td>\n | Optimal threshold value<\/td>\n<\/tr>\n | \n| Step 4<\/td>\n | Set difference-to-open at identified threshold. Recalibrate quarterly — the optimal threshold shifts as broker LP relationships and market volatility regimes change.<\/td>\n | Deployed filter parameter<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nThree structural limitations<\/h3>\n\n \n LIMITATION 1<\/div>\n Large latency events pass through<\/h3>\nHigh-volatility periods create large price movements. A feed latency artifact during a 10-pip move can appear as a 4–5 pip discrepancy between brokers. A 3-pip threshold does not catch this. Large latency events are the most damaging — largest losses and most visible toxic flow pattern.<\/p>\n<\/p><\/div>\n \n LIMITATION 2<\/div>\n Static threshold, dynamic market<\/h3>\nThe optimal threshold varies with market conditions. During Asian session quiet periods, a 1.5-pip threshold may filter adequately. During London open, the same threshold passes a high proportion of latency artifacts. A fixed threshold is always a compromise.<\/p>\n<\/p><\/div>\n \n LIMITATION 3<\/div>\n No directional awareness<\/h3>\nThe simple filter treats all discrepancies above the threshold identically regardless of market context at the moment of signal detection. It cannot distinguish a 3-pip genuine LP discrepancy from a 3-pip latency artifact produced by a rapid price event.<\/p>\n<\/p><\/div>\n<\/div>\n Advanced filter: fast feed reference architecture<\/h2>\n\n The fast feed filter introduces a third independent data source — faster than either execution broker — as the classification mechanism for each detected discrepancy.<\/strong> Instead of filtering by magnitude alone, the system uses the fast feed to determine whether a detected discrepancy coincides with a price movement event on the reference feed. If it does, the signal is latency-induced and discarded. If the reference feed is quiescent, the discrepancy is classified as a genuine LP difference and execution proceeds.<\/p>\n<\/div>\nThe classification logic at each signal detection event:<\/p>\n Signal classified as GENUINE LP DISCREPANCY if ALL conditions are true:<\/p>\n (1) FastFeed.RateOfChange(last 100ms) < MovementThreshold
\n — Reference feed has not moved significantly in the preceding window
\n — No directional price event currently propagating through the market<\/p>\n (2) FastFeed.LastTickAge < StalenessThreshold
\n — Reference feed is actively updating (not stale or disconnected)
\n — Ensures classification check is based on live data<\/p>\n (3) Discrepancy.Persistence > MinPersistenceWindow
\n — Discrepancy has existed for at least N milliseconds
\n — Genuine LP discrepancies persist; latency artifacts collapse in 30–100ms<\/p>\n Signal classified as LATENCY-INDUCED if ANY condition fails → order discarded.<\/p><\/div>\n Condition 1: Rate-of-change on the fast feed<\/h3>\nThis is the primary classification condition. The fast reference feed is faster than both execution brokers — it receives global market events before either broker’s quote updates. If the reference feed shows significant price movement in the window preceding signal detection, this movement is the probable cause of the apparent discrepancy: one execution broker’s feed updated from the event, the other has not yet.<\/p>\n \n\n\n| Parameter<\/th>\n | Typical value<\/th>\n | Note<\/th>\n<\/tr>\n<\/thead>\n | \n\n| MovementThreshold<\/td>\n | 0.5–1.5 pips per 100ms for major pairs; 1.5–3.0 pips for volatile pairs<\/td>\n | Set by measuring typical pip movement per 100ms in normal vs event conditions for the specific instrument<\/td>\n<\/tr>\n | \n| Lookback window<\/td>\n | 50–200ms<\/td>\n | Must capture the movement event but not mask genuine discrepancies following a movement event with a delay. Calibrated from measured feed latency differential.<\/td>\n<\/tr>\n | \n| Staleness threshold<\/td>\n | 500ms–2,000ms<\/td>\n | If the reference feed has not updated within this window, it may be stalled. Treat signals during staleness events conservatively — discard or hold until feed resumes.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nWhy the fast feed filter is qualitatively superior<\/h3>\n\n \n ADVANTAGE 1<\/div>\n Catches large latency events<\/h3>\nA 5-pip latency artifact during a major price event is classified as latency-induced by the fast feed filter — regardless of magnitude. The simple threshold would pass it if set below 5 pips. The fast feed filter classifies based on market state, not discrepancy size.<\/p>\n<\/p><\/div>\n \n ADVANTAGE 2<\/div>\n Dynamically adapts to volatility<\/h3>\nDuring quiet periods, the reference feed shows low rate-of-change and classification rarely triggers. During volatile periods, the reference feed is active and classifies latency artifacts continuously. The filter automatically tightens during high-risk periods without manual adjustment.<\/p>\n<\/p><\/div>\n \n ADVANTAGE 3<\/div>\n Retains small genuine signals<\/h3>\nA genuine 0.8-pip LP discrepancy that the simple threshold would block passes the fast feed filter if the reference feed is quiescent. The filter does not sacrifice small genuine signals to avoid small latency signals — each signal is classified independently on market context.<\/p>\n<\/p><\/div>\n \n ADVANTAGE 4<\/div>\n Near-complete latency elimination<\/h3>\nIn well-calibrated deployments, the fast feed filter reduces latency-induced contamination from 60–80% of unfiltered signals to under 5%. The remaining contamination consists of edge cases where a price event is slow enough not to trigger the rate-of-change threshold but fast enough to create a feed differential.<\/p>\n<\/p><\/div>\n<\/div>\n Filter comparison<\/h2>\n\n\n\n| Filter<\/th>\n | Latency rejection<\/th>\n | Genuine retention<\/th>\n | Complexity<\/th>\n | Best for<\/th>\n<\/tr>\n<\/thead>\n | \n\n| No filter<\/td>\n | 0% — all pass<\/td>\n | 100%<\/td>\n | None<\/td>\n | Not viable — toxic flow guaranteed<\/td>\n<\/tr>\n | \n| Difference-to-open only<\/td>\n | 40–60%<\/td>\n | 80–90%<\/td>\n | Low<\/td>\n | Initial setups, closely-matched broker feed speeds<\/td>\n<\/tr>\n | \n| Difference-to-open + persistence<\/td>\n | 60–75%<\/td>\n | 75–85%<\/td>\n | Low<\/td>\n | Improved baseline, still misses large latency events<\/td>\n<\/tr>\n | \n| Fast feed filter (full)<\/td>\n | 90–97%<\/td>\n | 85–95%<\/td>\n | High<\/td>\n | Production arbitrage, hostile broker environments<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n Calibration sequence for the fast feed filter<\/h3>\n\n- Phase 1:<\/strong> Run in logging mode for 5–10 days. Record every detected discrepancy with full context: all feed states, discrepancy magnitude, persistence duration, and reference feed rate-of-change in preceding 100ms and 200ms windows.<\/li>\n
- Phase 2:<\/strong> Post-hoc classify each logged signal as genuine (persists over 150ms, reference feed quiescent) or latency-induced (collapses under 100ms, reference feed active at detection time).<\/li>\n
- Phase 3:<\/strong> Test different combinations of MovementThreshold, lookback window, and MinPersistenceWindow against the classified dataset. Target: genuine retention above 85%, latency pass-through below 8%.<\/li>\n
- Phase 4:<\/strong> Deploy with optimised parameters on minimum lot size. Monitor P&L attribution by signal type for the first 10 trading days. Recalibrate quarterly or after significant market regime changes.<\/li>\n<\/ul>\n<\/div>\n
Frequently asked questions<\/h2>\n\n What is the difference between a genuine LP discrepancy and a latency-induced discrepancy?<\/div>\n \n A genuine LP discrepancy exists because two brokers’ liquidity providers are pricing the same instrument differently — a structural difference in how each LP models the market or manages inventory. A latency-induced discrepancy exists because one broker’s feed received a market event faster than the other. Genuine discrepancies are tradeable and persist for 200ms to 2,000ms. Latency artifacts collapse within 30–150ms as the slower feed catches up — typically before orders can arrive at the slower broker.<\/p>\n<\/div>\n What is difference-to-open and how does it help?<\/div>\n \n Difference-to-open is a configurable minimum price discrepancy — in pips — that must exist between two broker quotes before any order is placed. It filters latency-induced signals by exploiting the tendency for feed-latency artifacts to be smaller on average than genuine LP discrepancies. It is effective at eliminating small latency signals but does not catch large latency events during high-volatility periods where a fast price movement creates a large apparent discrepancy between feeds with different update speeds.<\/p>\n<\/div>\n What is the fast feed filter and how does it work?<\/div>\n \n The fast feed filter uses a third reference price feed — faster than both execution brokers — to classify each detected discrepancy before placing an order. If the reference feed shows significant price movement in the window preceding signal detection, the discrepancy is classified as latency-induced and discarded. If the reference feed is quiescent, the discrepancy is classified as a potential genuine LP difference and execution proceeds. This classifies signals based on market state rather than magnitude alone, catching large latency events that the simple threshold misses.<\/p>\n<\/div>\n Why does unfiltered hedge arbitrage create toxic order flow?<\/div>\n \n Latency-induced signals produce orders at the exact moment of price movement events. Broker risk systems detect this concentration as a technical flow pattern. Additionally, latency-induced trades consistently produce adverse fills and fast exits at small losses, creating an asymmetric hold-time and P&L distribution that further identifies the account as technical exploitation. Once classified, the account receives degraded execution that also affects the profitable genuine LP discrepancy trades.<\/p>\n<\/div>\n What is required for the fast feed filter?<\/div>\n \n A third price data source demonstrably faster than both execution brokers at receiving global market events. This can be a dedicated market data provider, a co-located price feed service, or a third broker account used as a reference feed only (no orders placed through it). The reference feed runs on a separate monitoring thread with hardware-level timestamps at socket receipt. No orders are ever placed through the reference feed — it is a classification input only.<\/p>\n<\/div>\n How often do filter parameters need to be recalibrated?<\/div>\n \n Quarterly minimum. The optimal parameters shift as broker LP relationships evolve, feed infrastructure changes, and market volatility regimes shift. Immediate recalibration is warranted when: a broker changes its LP or pricing engine; VPS provider or network routing changes affect feed latencies; or sustained changes in instrument volatility occur. SharpTrader’s per-signal attribution logging provides the data needed for ongoing calibration without a separate offline mode.<\/p>\n<\/div>\n<\/div>\n | | | |