English
Deutsch
日本語
العربية
한국어
Español
Português
Indonesia
中文
Phantom Drift wraps latency arbitrage logic inside RSI-triggered entries and a controlled averaging sequence. Broker detection systems see a conventional technical trader. The actual profit mechanism — lock arbitrage activating at drawdown depth via LockCL2 — produces no detectable order timing signature. This guide explains how Phantom Drift works, why it was built, and how to configure it.
Phantom Drift is a SharpTrader strategy that uses RSI-based entries and a controlled averaging sequence as the visible trade structure — while latency and lock arbitrage operate as the underlying profit mechanism. The broker’s risk system sees RSI-triggered entries, occasional averaging, and limit-order exits: an account profile consistent with thousands of other RSI-based automated strategies. The actual profit driver — fast-feed arbitrage unlocking at drawdown depth — leaves no detectable trace at the order timing level.
The name reflects the core design: arbitrage profits that appear to come from nowhere — like a ghost. The visible trade structure is the mask; the arbitrage is the mechanism. Phantom Drift was developed in response to increasing broker sophistication in detecting direct latency arbitrage, particularly the timestamp correlation analysis that became standard after 2018.
Direct latency arbitrage is now detectable by most major brokers within weeks of consistent use. The detection mechanism is straightforward: orders placed within milliseconds of a fast-feed price update produce a statistically distinct timestamp correlation pattern. Modern broker risk systems scan order logs automatically and flag accounts where order timing correlates with feed update events above a statistical threshold.
| Detection vector | Direct latency arb | Phantom Drift |
|---|---|---|
| Order timing | Orders at fast-feed events — detectable within weeks | RSI-triggered entries — no fast-feed correlation |
| Hold time | Sub-10 second holds — primary flag | Minutes to hours — normal profile |
| Win rate | 85–95% — statistically impossible for technical trading | 60–75% — plausible RSI averaging range |
| Exit pattern | Market orders at signal moments | Limit orders at price levels — looks like TP placement |
| Detection timeline | Weeks to months | Months to years at same broker |
Every Phantom Drift trade cycle passes through six phases. Phases 1–3 are fully visible to the broker. Phases 4–5 are entirely internal. Phase 6 appears as a standard limit-order exit.
| Phase | What happens | Broker visibility |
|---|---|---|
| 1 — RSI monitoring | Phantom Drift monitors RSI on the configured timeframe. Fast feed runs in parallel, independently tracking price. No orders placed. | Nothing visible |
| 2 — RSI entry | RSI reaches configured oversold or overbought threshold. Phantom Drift opens an initial position. This is the visible entry trigger — identical to any RSI strategy. | Standard RSI entry visible |
| 3 — Averaging | Position moves against the RSI signal. Phantom Drift adds to the position at configured intervals, building the drawdown depth that LockCL2 requires. | Averaging sequence visible — conventional pattern |
| 4 — Lock activates | At configured drawdown depth, LockCL2 activates internally. Position is hedged. Fast feed now monitors for the unlock signal. No orders sent to broker yet. | Nothing — fully internal |
| 5 — Unlock detected | Fast feed signals the unlock. LockCL2 places a virtual limit order at the target price level inside SharpTrader’s memory. Still nothing sent to broker. | Nothing — fully internal |
| 6 — Exit at price level | Market price reaches the virtual order’s level. SharpTrader sends the real order to the broker. Position closes at profit. | Limit order exit at price level — looks like planned TP |
RSI-triggered entries at oversold/overbought levels — entry timing correlates with RSI threshold crossings, not fast-feed events. Averaging sequence with configurable lot multiplier. Positions held minutes to hours. Exit via limit orders at price levels, not market orders triggered by external signals. Win rate 60–75%. Account profile: RSI-based automated strategy with averaging and disciplined exits. Consistent with thousands of other accounts at the same broker.
RSI threshold crossing triggers entry. Entry timing correlates with RSI signal, not fast-feed events. No statistical correlation between order placement and price feed updates.
RSI condition activates the averaging sequence, which creates the drawdown depth LockCL2 requires to run lock arbitrage. RSI is the structural trigger; the fast feed is the profit signal.
Limit orders at price levels. Hold times minutes to hours. Varied exit prices across trades. Consistent with a technical trader staging out of an averaging position.
LockCL2 virtual orders trigger when the fast feed detects the unlock signal. The broker receives the order only when price reaches the configured level — appearing identical to a planned limit exit.
60–75% overall. Losing trades occur regularly. Distribution consistent with a well-configured averaging strategy that accepts occasional full-averaging losses.
Controlled losing trades are deliberately introduced into the averaging sequence to keep win rate in the non-suspicious range. These are structural design decisions, not strategy failures.
| Factor | Direct latency arb | Phantom Drift |
|---|---|---|
| Entry trigger | Fast-feed signal → instant market order | RSI threshold → entry (fast feed runs in parallel) |
| Broker detection | Detected within weeks — timestamp correlation | Not detected — RSI timing, no fast-feed correlation |
| Profit mechanism | Latency edge on fast-feed entry | LockCL2 lock arbitrage unlocking at drawdown depth |
| Hold time | Seconds — flagged | Minutes to hours — normal profile |
| Win rate | 85–95% — flagged | 60–75% — plausible range |
| Margin requirement | Standard (1 position) | Higher (averaging layers + hedge) |
| Prop firm viability | Banned and detected | Viable — RSI averaging passes statistical review |
| Longevity at one broker | Weeks to months | Months to years |
The trade-off: Phantom Drift requires more capital per trade (averaging sequence + hedge layers) and is slower to cycle than direct latency arbitrage. For traders who prioritise account longevity and prop firm compatibility over maximum throughput, Phantom Drift is the preferred configuration.
Set the RSI period (default 14) and oversold/overbought thresholds (default 30/70). Tighter thresholds (20/80) produce fewer but higher-conviction entries. Looser thresholds (35/65) increase trade frequency.
Configure the number of averaging layers and the lot size multiplier at each layer. More layers create deeper drawdown for lock arbitrage but require more margin. Typical setup: 3–5 layers, 1.5–2× multiplier.
The drawdown level at which LockCL2 activates and the hedge is applied. Set relative to account size and the instrument’s typical volatility range. Shallower = faster cycles, smaller recovery per trade.
Connect any external data source with a speed advantage over the execution broker. Configured independently of the RSI signal source. A 50–100ms advantage over the broker is the practical minimum.
Configure the frequency of deliberately losing trades in the averaging sequence — positions closed at a small loss rather than proceeding to the lock phase. Keeps the overall win rate in the non-suspicious range.
Per-trade hard stop loss and account equity protection level. Required for prop firm accounts. Applies automatically to every Phantom Drift trade regardless of the averaging depth reached.
Phantom Drift was specifically designed to be viable on prop firm accounts where direct latency arbitrage is explicitly prohibited. The RSI entry structure and averaging sequence produce an account profile that passes standard prop firm statistical review.
| Prop firm | Compatibility | Key notes |
|---|---|---|
| FTMO | Compatible | RSI averaging profile passes statistical review. Hard stop and equity control cover daily loss and drawdown limits. Do not use on cTrader or MatchTrader accounts at FTMO — EAs prohibited on those platforms there. |
| FundedNext | Compatible | Algorithmic strategies permitted with risk rule compliance. SharpTrader’s compliance settings cover 5-day minimum, daily loss limit, and equity control requirements. |
| The5%ers | Compatible | Broadly permissive algorithmic rules. 4% max drawdown — configure equity control to 96% threshold. Phantom Drift averaging profile consistent with permitted strategies. |
| Firms prohibiting averaging | Not compatible | If a prop firm explicitly prohibits martingale-style or averaging position building, the Phantom Drift averaging sequence violates that rule regardless of masking. Always review firm-specific terms before deploying. |
Phantom Drift is a SharpTrader strategy that masks latency and lock arbitrage inside an RSI-triggered entry and averaging sequence. Broker detection systems see RSI-based technical trading with limit-order exits. The actual profit mechanism — LockCL2 lock arbitrage unlocking at drawdown depth — produces no detectable order timing signature at the broker level.
Three mechanisms simultaneously: (1) RSI entry triggers eliminate the timestamp correlation between fast-feed events and order placement — entries correlate with RSI threshold crossings, not price feed updates; (2) the averaging sequence normalises hold times from sub-10-second to minutes-to-hours; (3) deliberately controlled losing trades bring the overall win rate into the 60–75% range that is plausible for a technical averaging strategy. All three primary detection vectors are neutralised simultaneously.
Yes, for most major prop firms. The RSI averaging profile is consistent with permitted algorithmic strategies at FTMO, FundedNext, and The5%ers. Configure SharpTrader’s compliance settings — hard stop, equity control, end-of-day close — to meet each firm’s specific risk rules. Do not use at firms that explicitly prohibit averaging or martingale-style position building.
Direct latency arbitrage fires orders immediately on fast-feed signals — creating detectable timestamp correlation that most brokers identify within weeks. Phantom Drift uses RSI signals as the visible entry trigger, with the fast feed operating as the internal signal for lock arbitrage at drawdown depth. Broker sees RSI-triggered entries with limit exits. Detection timeline: direct latency arbitrage — weeks to months; Phantom Drift — months to years at the same broker.
Yes. LockCL2 — the lock arbitrage component inside Phantom Drift — requires a price feed with a measurable speed advantage over the execution broker. Any external data source faster than the broker works: external data providers, a second broker account used as a reference feed only. A 50–100ms advantage is the practical minimum. SharpTrader connects to the fast feed independently of the RSI signal source.
More. The averaging sequence adds to the position across multiple layers before the lock activates, and the lock itself adds a hedge position on top. Total margin exposure per trade cycle is significantly higher than a single direct latency arbitrage position. Account sizing must account for the full averaging depth plus the hedge margin. This higher capital requirement is the direct trade-off for the improved account longevity and detection resistance.
RSI entry masking · Virtual order management · Prop firm compliance built-in · 25 years of arbitrage development