Advertisement IC Markets

Unlocking the Smart Money Play: Why You Need a Liquidity Sweep Detector for Forex Scalping

Discuss 1-minute to 15-minute price action setups, fading intraday momentum, key support/resistance zones, and proven short-term trading methodologies.
PTScalper
Site Admin
Posts: 7821
Joined: Mon Jul 20, 2026 1:28 pm

Re: Unlocking the Smart Money Play: Why You Need a Liquidity Sweep Detector for Forex Scalping

Post by PTScalper »

Key additions to note:

⁠request.security()⁠: This line (⁠htfEma = request.security(...)⁠) calculates the 50 EMA on the 4-hour chart and maps that exact value down to your 15-minute or 5-minute candles.
The Bypass Toggle (⁠useFilter⁠): The variables ⁠htfBullish⁠ and ⁠htfBearish⁠ are designed so that if you uncheck "Enable HTF Filter" in the script settings, the variables default to ⁠true⁠. This bypasses the logic without requiring you to delete code, allowing you to seamlessly test the strategy with and without the trend filter.

Execution Gating: The execution signals at the very bottom now require both the structural reclaim (⁠isHighReclaim⁠ / ⁠isLowReclaim⁠) and the trend alignment (⁠htfBearish⁠ / ⁠htfBullish⁠) to evaluate as true before painting an arrow.
Preserve your own money. Scale with the market's money. Exponential growth is the ultimate key.
Recommended broker for automated trading & scalping IC Markets
LondonScalper
Posts: 965
Joined: Sat Sep 05, 2026 7:54 am

Re: Unlocking the Smart Money Play: Why You Need a Liquidity Sweep Detector for Forex Scalping

Post by LondonScalper »

PTScalper wrote:Price action at a key level is a question; the time spent beyond that level is the answer.
That’s the useful filter — not “detector said sweep.”

I treat a spike through Asia low into a marked demand block as a candidate only if HTF is already aligned and the reclaim is fast. If price parks beyond the level, prints acceptance, and time-of-day is a genuine session drive (London continuation, NY news), I stop calling it a sweep and treat it as a break. Speed of reclaim beats the label.

Desk rule: fade only with invalidation beyond the sweep extreme and a time stop. A clean HTF-with-trend sweep at the London open is one trade. The same wick in the middle of a dead book is just a thin print. Indicator alerts don’t get a vote if those three — structure, clock, reclaim — disagree.
PropScalpDesk
Posts: 521
Joined: Sat Sep 19, 2026 7:50 pm

Re: Unlocking the Smart Money Play: Why You Need a Liquidity Sweep Detector for Forex Scalping

Post by PropScalpDesk »

PTScalper wrote:To code this, you need a state machine... a true sweep is a sequence of events tied to a strict time limit.
Sweep detectors help when they encode sequence and time-in-zone, not when they spray arrows. Box Asia, watch for liquidity take, require reclaim inside a max bar count, optionally filter with HTF. That architecture matches discretionary rules I already run by hand on London open.

I still want human veto: spread gate, news blackout, correlation cap. Code that cannot see firm rules will happily signal through a challenge fail. Pine is fine for visualisation; live size still waits on execution reality.

Frankfurt desk: indicators highlight permission; they do not get the click. If reclaim is late beyond your time limit, it is a different trade — usually a pass.

Alerts on my desk are watchlist-only until a long sample of alerts-plus-manual veto looks clean. Auto-attached size through a firm news window is how automation donates evaluations.

Do you run sweep alerts as watchlist only, or auto-attached with micro size after a long demo sample?
LondonNewsTrader
Posts: 421
Joined: Mon Sep 21, 2026 9:30 am

Re: Unlocking the Smart Money Play: Why You Need a Liquidity Sweep Detector for Forex Scalping

Post by LondonNewsTrader »

PTScalper wrote: Ensure your TradingView chart timezone matches your mental model (e.g., if you consider Asia to be 18:00 to 02:00 EST, set your chart to New York time).
I don't think that's right for Pine. The time() function with a session string uses the exchange time zone of the symbol, syminfo.timezone, unless a time zone argument is passed. The chart's time zone setting only changes how the axis is displayed; it doesn't change what the script calculates. So setting the chart to New York time won't move the Asian window. For FX the exchange time zone depends on the data feed, which is why the same script can behave differently on two brokers' symbols.

The fix is simple: pass the time zone explicitly, for example time(timeframe.period, sess, "America/New_York"), and the window will follow New York daylight saving automatically.

The 1-bar versus 2-bar setting is a useful option. I'd expect the 2-bar version to catch more of the sweeps that happen on data releases, where the first candle often closes beyond the level before the second one reverses it.
FXS Prop Desk
Posts: 1689
Joined: Wed Oct 07, 2026 9:52 am

Re: Unlocking the Smart Money Play: Why You Need a Liquidity Sweep Detector for Forex Scalping

Post by FXS Prop Desk »

PTScalper wrote:Price action at a key level is a question; the time spent beyond that level is the answer.
That sentence is a good rule of thumb. To make it measurable, set a maximum number of M1 or M5 bars outside the level before the reclaim must happen, for example three bars. If price stays outside longer, treat it as a breakout regardless of how it looks. Testing different bar counts on your own pair data will show which value best separates sweeps from real breaks.
FXS Official Team | The Idea Lab & Strategy
Post Reply