{"id":12937,"date":"2026-05-04T14:14:52","date_gmt":"2026-05-04T14:14:52","guid":{"rendered":"https:\/\/bjftradinggroup.com\/?page_id=12937"},"modified":"2026-05-04T14:18:50","modified_gmt":"2026-05-04T14:18:50","slug":"lock-arbitrage","status":"publish","type":"page","link":"https:\/\/bjftradinggroup.com\/pt\/lock-arbitrage\/","title":{"rendered":"lock Arbitrage"},"content":{"rendered":"

<\/p>\n

\n
\n BJF TRADING GROUP  ·  SHARPTRADER PRO<\/span><\/p>\n

Lock Arbitrage: All 4 Variants Explained<\/span> — Lock, LockCL1, LockCL2, LockCL3<\/h1>\n

\n Lock arbitrage holds opposing positions on two separate broker accounts simultaneously<\/strong>, eliminating net market exposure. Profit comes from selectively closing one leg at the right moment — guided by a fast price feed. SharpTrader includes four lock variants plus BrightDuo and BrightTrio Plus masking systems. This guide explains each variant, when to use it, and how they differ.\n <\/p>\n

\n 2,800<\/strong> words<\/span>
\n 10<\/strong> sections<\/span>
\n ~13 min<\/strong> read<\/span>
\n Audience:<\/strong> arbitrage traders, multi-broker setups, prop firm traders<\/span>\n <\/div>\n<\/div>\n
\n
4<\/span>Lock variants<\/span><\/div>\n
2<\/span>Masking systems<\/span><\/div>\n
0<\/span>Net market exposure<\/span><\/div>\n
25 yrs<\/span>BJF development<\/span><\/div>\n<\/div>\n

What is lock arbitrage — in one paragraph<\/h2>\n
\n

Lock arbitrage simultaneously holds a buy position on one broker account and an equal sell position on a second account for the same instrument.<\/strong> The opposing positions cancel out market exposure — the combined P&L is “locked” at a fixed level regardless of price movement. A fast price feed then detects the optimal moment to close one leg, converting the flat locked position into a net profit equal to the captured spread between the two brokers’ quotes.<\/p>\n<\/div>\n

The profit source is the pricing difference between two independent liquidity providers. Different brokers receive market data at different speeds, apply different markup models, and source quotes from different LP relationships. These differences create transient cross-broker discrepancies that a well-configured lock arbitrage system can capture.<\/p>\n

\n

Why lock arbitrage does not require millisecond execution<\/h3>\n

Unlike pure latency arbitrage — where the entire edge can collapse in under 50ms — lock arbitrage works by managing an existing position. The unlock window from when the fast feed fires to when the slow broker’s quote converges is typically seconds rather than milliseconds<\/strong>. This makes lock arbitrage viable on a wider range of broker connections and VPS configurations.<\/p>\n<\/div>\n

The five-step lock arbitrage sequence<\/h2>\n

All four variants share the same underlying sequence. The differences between them lie in how they handle the closing trigger, netting account constraints, and broker-side detection avoidance.<\/p>\n\n\n\n\n\n\n\n\n\n
Step<\/th>\nAccount A<\/th>\nAccount B<\/th>\nNet exposure<\/th>\n<\/tr>\n<\/thead>\n
1 — Signal fires<\/td>\nOpens BUY 1 lot EURUSD @ 1.08490<\/td>\nNo position<\/td>\nLong 1 lot<\/td>\n<\/tr>\n
2 — Lock applied<\/td>\nBUY remains open<\/td>\nOpens SELL 1 lot EURUSD @ 1.08490<\/td>\nZero — locked<\/td>\n<\/tr>\n
3 — Fast feed watches<\/td>\nBUY holds<\/td>\nSELL holds<\/td>\nZero — any price move<\/td>\n<\/tr>\n
4 — Unlock signal<\/td>\nBUY now profitable as price moves up<\/td>\nSELL closed at lock price (cheap)<\/td>\nLong 1 lot running<\/td>\n<\/tr>\n
5 — Close BUY<\/td>\nBUY closes at profit<\/td>\nFlat<\/td>\nNet profit realized<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

At lock: Account A = −X pips, Account B = +X pips, net = 0. After unlock: Account A closes at +Y pips (price moved up), Account B closed near 0 (before slow feed updated). Net = +Y minus spreads. The fast feed’s advance notice of direction is what makes Y consistently positive.<\/p>\n

Lock (Base) — min time and min pips trigger<\/h2>\n
\n

The base Lock strategy is designed for brokers that enforce a minimum holding period or a minimum pip movement before a position can be closed.<\/strong> Instead of waiting for an arbitrage signal as the closing trigger, it uses a configurable time threshold, a pip distance threshold, or both simultaneously — whichever fires first.<\/p>\n<\/div>\n

\n
\n
MIN TIME TRIGGER<\/div>\n

⏳ Time-based close<\/h3>\n

After the lock is applied, a timer starts. Both positions close when the configured minimum holding time elapses, regardless of price movement. For brokers that flag accounts closing positions too quickly — typically 30–120 seconds minimum.<\/p>\n<\/p><\/div>\n

\n
MIN PIPS TRIGGER<\/div>\n

📏 Distance-based close<\/h3>\n

Both positions close once price has moved a configured minimum number of pips from the lock entry level. For brokers that reject close orders placed less than X pips from the open price. Either condition closing both legs simultaneously.<\/p>\n<\/p><\/div>\n<\/div>\n

Best for:<\/strong> Brokers with explicit minimum hold time rules (e.g. 30-second minimum) or minimum pip distance before close is permitted. The base Lock respects these constraints while still capturing the cross-broker spread.<\/p>\n

LockCL1 — netting and FIX API accounts<\/h2>\n
\n

LockCL1 is designed specifically for netting accounts — common on FIX API and cTrader connections — where opening an opposing position on the same instrument automatically cancels the existing one.<\/strong> On netting accounts, the standard lock (long + short on the same account) is impossible. LockCL1 routes each leg strictly to a separate account and uses the next arbitrage signal — not a time or pip threshold — as the closing trigger.<\/p>\n<\/div>\n\n\n\n\n\n\n\n
Step<\/th>\nAction<\/th>\nNote<\/th>\n<\/tr>\n<\/thead>\n
Step 1<\/td>\nOpens first order on Account A by arbitrage signal. Trails the position.<\/td>\nWhen closing trigger fires, opens hedge on Account B only — never on Account A<\/td>\n<\/tr>\n
Step 2<\/td>\nOn next arbitrage signal, closes one of the two open positions.<\/td>\nBUY signal closes the SELL on B. SELL signal closes the BUY on A.<\/td>\n<\/tr>\n
Step 3<\/td>\nTrails the remaining position and closes by configured trigger (TP, SL, trailing, or lifetime).<\/td>\nReturns to Step 1 for next cycle<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Best for:<\/strong> FIX API accounts and cTrader connections where netting execution is the standard. LockCL1 never creates a situation where a buy and sell for the same symbol exist simultaneously on a single account — fully compatible with netting execution models.<\/p>\n

LockCL2 — core strategy with virtual orders<\/h2>\n
\n

LockCL2 is the primary lock arbitrage strategy and the foundation for LockCL3, BrightDuo, and BrightTrio Plus.<\/strong> It introduces virtual orders — positions tracked inside SharpTrader’s memory rather than sent to the broker immediately — to eliminate the re-entry timestamp correlation that makes standard lock arbitrage detectable by broker risk systems.<\/p>\n<\/div>\n

The detection problem LockCL2 solves<\/h3>\n

In standard lock arbitrage, when an unlock signal fires, the re-entry order is sent to the broker at the exact moment of a fast-feed event. Broker risk systems scan order logs for orders placed within milliseconds of price feed updates — a statistically distinct pattern that identifies lock arbitrage. LockCL2 decouples the signal from the order entirely.<\/p>\n

\n
\n
STANDARD LOCK<\/div>\n

❌ Direct re-entry (detectable)<\/h3>\n

Re-entry order sent to broker at signal time. Timestamp correlates with fast-feed event. Detectable by order timing analysis. Account flagged within weeks of consistent use.<\/p>\n<\/p><\/div>\n

\n
LOCKCL2<\/div>\n

✔ Virtual re-entry (not detectable)<\/h3>\n

Re-entry managed internally inside SharpTrader. Broker only sees the order when market price reaches the configured level — indistinguishable from a standard limit order placed by a technical trader.<\/p>\n<\/p><\/div>\n<\/div>\n

LockCL2 step-by-step<\/h3>\n\n\n\n\n\n\n\n\n\n
Step<\/th>\nWhat happens<\/th>\nBroker sees<\/th>\n<\/tr>\n<\/thead>\n
1 — Entry<\/td>\nOpens first order on Account A by arb signal. Trails it. When closing trigger fires, opens opposing position on Account B. Lock created.<\/td>\nTwo real opposing orders<\/td>\n<\/tr>\n
2 — Signal while locked<\/td>\nNew arb signal arrives. CL2 closes position opposite to signal direction. Simultaneously creates a virtual order<\/em> in the same direction as the remaining real position — inside SharpTrader’s memory only.<\/td>\nOne real position closed, one remaining<\/td>\n<\/tr>\n
3 — Virtual tracking<\/td>\nVirtual order has its own SL, TP, and trailing stop. SharpTrader tracks price internally. Nothing sent to broker yet.<\/td>\nOnly Account A’s remaining position visible<\/td>\n<\/tr>\n
4 — Virtual hits target<\/td>\nWhen the virtual order’s SL, TP, or trailing stop is triggered by price movement, SharpTrader reopens the closed real position on Account B.<\/td>\nNew order at current market price — looks like an independent entry<\/td>\n<\/tr>\n
5 — Lock restored<\/td>\nBoth accounts hold real opposing orders. Strategy waits for next arb signal.<\/td>\nNormal two-account position<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Best for:<\/strong> Standard retail broker hedging accounts for general-purpose lock arbitrage. Best balance of performance and detection resistance. The recommended starting point for most lock arbitrage setups.<\/p>\n

LockCL3 — active and passive account model<\/h2>\n
\n

LockCL3 is a CL2 modification for setups where one broker offers superior execution and the other is slower or more restricted but suitable for the hedge leg.<\/strong> In CL3, one account is designated active — all arbitrage entries flow through it. The other is passive — holds only the hedging position and never receives arbitrage entries.<\/p>\n<\/div>\n

\n
\n
LOCKCL2 BEHAVIOUR<\/div>\n

Both accounts active<\/h3>\n

Enters arbitrage deals alternately on both accounts. Both must handle fast execution. Every second cycle routes to the other account — requiring both to be capable of rapid order processing.<\/p>\n<\/p><\/div>\n

\n
LOCKCL3 BEHAVIOUR<\/div>\n

One account active only<\/h3>\n

All arbitrage entries flow to the active account only. The passive account holds the hedge position exclusively. Only the fast broker needs rapid execution — the slow broker just holds the hedge.<\/p>\n<\/p><\/div>\n<\/div>\n

To configure passive mode: in SharpTrader’s strategy Settings tab, uncheck Allow arbitrage<\/strong> for the slow account. It continues to hold its hedging position and participate in lock\/unlock cycles — but never receives an arbitrage order entry.<\/p>\n

Best for:<\/strong> Mixed broker pairs where one offers FIX API with tight spreads and the other is slower or more restricted but usable for hedging. All profitable arbitrage flows through the fast account only.<\/p>\n

All variants compared<\/h2>\n\n\n\n\n\n\n\n\n\n\n
Variant<\/th>\nClosing trigger<\/th>\nNetting OK?<\/th>\nVirtual orders<\/th>\nBest for<\/th>\n<\/tr>\n<\/thead>\n
Lock (Base)<\/td>\nMin Time OR Min Pips<\/td>\nYes<\/td>\nNo<\/td>\nBrokers with minimum hold \/ pip requirements<\/td>\n<\/tr>\n
LockCL1<\/td>\nArb signal + closing trigger<\/td>\nDesigned for netting<\/td>\nNo<\/td>\nFIX API \/ cTrader netting accounts<\/td>\n<\/tr>\n
LockCL2<\/td>\nVirtual order SL \/ TP \/ trailing<\/td>\nNeeds hedging<\/td>\nYes<\/td>\nStandard retail broker hedging accounts, general use<\/td>\n<\/tr>\n
LockCL3<\/td>\nVirtual order SL \/ TP \/ trailing<\/td>\nNeeds hedging<\/td>\nYes<\/td>\nMixed fast + slow broker pairs<\/td>\n<\/tr>\n
BrightDuo<\/td>\n3-level virtual trailing<\/td>\nNeeds hedging<\/td>\nYes<\/td>\nHigh-monitoring brokers, maximum longevity<\/td>\n<\/tr>\n
BrightTrio Plus<\/td>\n3-account rotation + virtual<\/td>\nNeeds hedging<\/td>\nYes<\/td>\nMultiple funded accounts at same prop firm<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

BrightDuo and BrightTrio Plus — advanced masking<\/h2>\n

BrightDuo — 3-level trailing for 2-account setups<\/h3>\n

BrightDuo is an advanced LockCL2 modification with virtual orders and up to three trailing levels. Instead of exiting at a single consistent threshold, BrightDuo stages exits across up to three configured price levels — each with its own trailing parameters. This produces a non-mechanical exit pattern consistent with a sophisticated technical trader managing a position with multiple target levels.<\/p>\n

\n

What BrightDuo eliminates<\/h3>\n
    \n
  • Re-entry timestamp correlation<\/strong> — virtual orders ensure broker sees limit orders at price levels, not orders timed to fast-feed events<\/li>\n
  • Short-hold win rate pattern<\/strong> — multi-level trailing naturally extends hold times to the minutes-to-hours range<\/li>\n
  • Mechanical exit pattern<\/strong> — three levels produce varied exit prices across trades; no two trades look identical<\/li>\n<\/ul>\n<\/div>\n

    BrightTrio Plus — 3-account rotation against cross-account detection<\/h3>\n

    Two-account lock arbitrage produces a recognisable cross-account P&L signature: Account A and Account B consistently show equal and opposite movements. Broker and prop firm risk systems that monitor multiple accounts per client flag this pattern within weeks.<\/p>\n

    BrightTrio Plus uses three accounts (A, B, C) where active, passive, and idle roles rotate in a non-repeating sequence:<\/p>\n\n\n\n\n\n\n\n\n
    Cycle<\/th>\nActive<\/th>\nHedge<\/th>\nIdle<\/th>\nA\/B mirror?<\/th>\n<\/tr>\n<\/thead>\n
    Cycle 1<\/td>\nA<\/td>\nB<\/td>\nC<\/td>\nThis cycle only<\/td>\n<\/tr>\n
    Cycle 2<\/td>\nB<\/td>\nC<\/td>\nA<\/td>\nNo — B now active<\/td>\n<\/tr>\n
    Cycle 3<\/td>\nC<\/td>\nA<\/td>\nB<\/td>\nNo — A now hedge<\/td>\n<\/tr>\n
    Result<\/td>\nEvery account has been active, passive, and idle across 3 cycles<\/td>\nNo persistent mirror detected<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Best for:<\/strong> Traders running multiple funded accounts at the same prop firm. BrightTrio Plus is the only viable solution when a prop firm’s risk system monitors cross-account P&L correlation.<\/p>\n

    Which variant to choose<\/h2>\n
    \n
    \n
    SITUATION 1<\/div>\n

    Broker enforces min hold or min pips<\/h3>\n

    Use Lock (Base)<\/strong>. Time + pip dual-trigger respects broker constraints while capturing the cross-broker spread.<\/p>\n<\/p><\/div>\n

    \n
    SITUATION 2<\/div>\n

    FIX API or cTrader netting accounts<\/h3>\n

    Use LockCL1<\/strong>. Only variant compatible with netting execution. Never opens opposing orders on the same account.<\/p>\n<\/p><\/div>\n

    \n
    SITUATION 3<\/div>\n

    Standard retail broker hedging accounts<\/h3>\n

    Use LockCL2<\/strong>. General-purpose. Virtual orders eliminate timestamp correlation. Best starting point for most setups.<\/p>\n<\/p><\/div>\n

    \n
    SITUATION 4<\/div>\n

    One fast broker + one slow broker<\/h3>\n

    Use LockCL3<\/strong>. All arbitrage through the fast account. Slow account holds hedge only — not burdened with speed requirements it cannot meet.<\/p>\n<\/p><\/div>\n

    \n
    SITUATION 5<\/div>\n

    Broker with active risk monitoring<\/h3>\n

    Use BrightDuo<\/strong>. Multi-level trailing and extended hold times neutralise all three primary detection vectors for 2-account lock arbitrage.<\/p>\n<\/p><\/div>\n

    \n
    SITUATION 6<\/div>\n

    Multiple funded accounts, same prop firm<\/h3>\n

    Use BrightTrio Plus<\/strong>. 3-account rotation eliminates cross-account P&L mirror signature — the only viable solution for multi-account prop firm environments.<\/p>\n<\/p><\/div>\n<\/div>\n

    Frequently asked questions<\/h2>\n
    \n
    What is lock arbitrage?<\/div>\n
    \n

    Lock arbitrage simultaneously holds a buy position on one broker account and a sell position on a second account for the same instrument, eliminating net market exposure. A fast price feed detects the optimal moment to close one leg — converting the flat locked position into a net profit. SharpTrader includes four variants (Lock, LockCL1, LockCL2, LockCL3) for different broker account types and conditions.<\/p>\n<\/div>\n

    What is the difference between Lock, LockCL1, LockCL2, and LockCL3?<\/div>\n
    \n

    Lock (Base) uses a time or pip threshold as the closing trigger — for brokers with minimum hold requirements. LockCL1 is for netting accounts (FIX API, cTrader) where opposing positions on the same account are not possible — it closes on the next arbitrage signal. LockCL2 is the general-purpose variant introducing virtual orders to eliminate detectable re-entry timing. LockCL3 is a CL2 modification where one account is passive (hedge only) and one is active (all arbitrage entries) — ideal when one broker is significantly faster than the other.<\/p>\n<\/div>\n

    What are virtual orders and why do they matter?<\/div>\n
    \n

    Virtual orders are positions tracked internally by SharpTrader rather than sent immediately to the broker. When a fast-feed signal fires in LockCL2 or LockCL3, the re-entry is managed as a virtual order with its own SL, TP, and trailing stop. The broker only receives a real order when the market price reaches the configured level — appearing as a standard limit order entry, not a fast-feed response. This eliminates the timestamp correlation pattern that broker risk systems use to identify lock arbitrage.<\/p>\n<\/div>\n

    What is BrightTrio Plus and when do I need it?<\/div>\n
    \n

    BrightTrio Plus uses three accounts (A, B, C) where active, passive, and idle roles rotate across all three. This breaks the cross-account P&L mirror signature of 2-account lock arbitrage — which prop firms monitoring multiple accounts per client detect within weeks. BrightTrio Plus is the recommended solution when running multiple funded accounts at the same prop firm simultaneously.<\/p>\n<\/div>\n

    Do I need hedging-enabled broker accounts for lock arbitrage?<\/div>\n
    \n

    For LockCL2, LockCL3, BrightDuo, and BrightTrio Plus — yes, accounts must permit hedging (simultaneous long and short on the same instrument). Standard retail broker hedging accounts support this by default. For LockCL1 — no, it is specifically designed for netting accounts (FIX API, cTrader). US brokers under FIFO rules cannot hold opposing positions and are incompatible with all variants except CL1 on properly routed FIX API connections.<\/p>\n<\/div>\n

    Can lock arbitrage be used on prop firm accounts?<\/div>\n
    \n

    With masking, yes. LockCL2 virtual orders eliminate the re-entry timestamp correlation for single-account prop firm use. BrightTrio Plus eliminates the cross-account mirror signature for traders running multiple funded accounts at the same firm. See the prop firm guide<\/a> for firm-by-firm compatibility details.<\/p>\n<\/div>\n<\/div>\n

    \n

    SharpTrader Pro — All Lock Variants in One Terminal<\/h2>\n

    Lock · LockCL1 · LockCL2 · LockCL3 · BrightDuo · BrightTrio Plus · 25 years of arbitrage development<\/p>\n

    Explore SharpTrader Pro →<\/a>
    \n     Prop Firm Guide →<\/a>\n<\/div>\n<\/div>\n