The Silver Bullet Setup: A Specific ICT-Style Time Window Strategy
Among the more specific, narrowly-defined setups circulating in advanced SMC and ICT-adjacent content, the Silver Bullet stands out for its unusually precise time-window definition — worth understanding directly given how specific and testable this particular concept is compared to some of the broader frameworks covered earlier in this series.
What the Silver Bullet Setup Specifically Defines
The setup identifies specific, narrow one-hour windows — commonly cited as roughly 10:00-11:00 AM New York time, and a similar window around the London open — during which a specific sequence is expected: a liquidity sweep (of a recent swing high or low) followed by a market structure shift and a retracement into an FVG or order block left by that shift, with entry taken on that retracement, all expected to complete and resolve within the single defined hour.
Why the Narrow Time Window Is the Defining, Distinguishing Feature
Unlike the broader session-based frameworks covered throughout this series (the full London open discussion, the NY session liquidity sweep post), the Silver Bullet's specific value proposition is its narrow, precisely bounded window — the claim is that this specific hour offers a disproportionately clean, reliable version of the liquidity-sweep-into-reversal pattern this series has covered extensively, compared to the same pattern's reliability across the broader session more generally.
Why This Narrow Specificity Makes the Concept Genuinely Testable
Connecting directly to the backtesting discipline covered throughout this series, the Silver Bullet's precise time-window definition makes it considerably easier to rigorously test than some of the broader, more qualitatively-defined concepts covered elsewhere (quarterly theory, IPDA) — a trader can specifically isolate trades occurring within this defined window and directly compare their performance against similar setups occurring outside it, providing a genuinely clear, quantifiable answer about whether this specific window offers the claimed edge for their own particular pairs and conditions.
A Reasonable, Skeptical Approach to Adopting This Specific Concept
Rather than assuming the claimed edge transfers automatically, apply the same rigorous, bar-by-bar backtesting process covered earlier in this series specifically to this narrow window, comparing setups within it against otherwise-similar setups occurring at other times — if your own data genuinely supports an edge specific to this window, it's a valuable, precisely-defined addition to your trading routine; if it doesn't, the broader session-based framework already covered throughout this series remains a perfectly sound foundation without this specific additional refinement.
Why Precise Time-Window Claims Deserve Extra Scrutiny
Given how many possible narrow time windows could be tested after the fact, and the genuine risk of over-fitting covered in the earlier over-optimization discussion, a specific, narrow time-window claim deserves particular skepticism until verified against a genuinely large, out-of-sample dataset — the same robustness-testing principles covered in the earlier curve-fitting post apply directly here, perhaps with even more weight given how easy it would be for a narrow window like this to have been identified through exactly the kind of after-the-fact historical fitting that post warned against.
The Underlying Point
The Silver Bullet setup offers a genuinely specific, testable refinement of the broader liquidity-sweep framework this series has covered throughout — its narrow, precise definition makes it easier to rigorously verify than several of the more qualitative concepts discussed elsewhere, but that same specificity also means it deserves the same careful, skeptical, out-of-sample testing this series has recommended for any narrowly-defined claim before being adopted as a core part of your trading routine.
Advertisement
Free SMC Trading Setups
Recommended broker for automated trading & scalping
Re: Free SMC Trading Setups
Optimal Trade Entry (OTE): Fibonacci Meets SMC
Optimal Trade Entry, commonly abbreviated OTE, describes a specific retracement zone — typically the area between the 61.8% and 79% Fibonacci retracement levels of a recent impulsive move — treated as the preferred entry area within the broader SMC framework, directly connecting to and extending the earlier Fibonacci mistakes post covered in this series.
Why This Specific Zone, Rather Than Any Single Fibonacci Level
Connecting directly to the earlier Fibonacci discussion, which noted the 61.8% level's rough alignment with SMC-relevant order block and discount/premium zones, OTE extends this into a defined range rather than a single precise level, on the reasoning that genuine institutional order block zones don't always sit at one exact Fibonacci ratio, but tend to cluster within this broader 61.8%-79% band across a large sample of genuine setups.
How This Connects Directly to the Premium/Discount Framework Covered Earlier
The OTE zone, sitting well within the deeper retracement portion of a move, generally corresponds to genuine discount territory (for a bullish setup) or premium territory (for a bearish setup) as covered in the earlier premium/discount post — meaning OTE is, in substance, a more specific, Fibonacci-quantified version of the same "enter in discount for longs, premium for shorts" principle already covered throughout this series, rather than an entirely separate, competing concept.
Why Combining OTE With Genuine Structural Confirmation Matters
Consistent with the earlier Fibonacci mistakes post's core caution, entering purely because price has reached the OTE zone, without the accompanying structural confirmation (a genuine order block or FVG within that zone, a lower-timeframe CHOCH confirming the retracement has concluded) risks exactly the standalone-Fibonacci-signal problem that post warned against — OTE should function as a refinement narrowing where within an already-identified structural zone your entry sits, not as an independent trigger replacing the structural confirmation this series has emphasized throughout.
A Practical Way to Use OTE Within the Broader Framework Already Covered
After identifying a genuine structural setup (a liquidity sweep, a confirmed CHOCH, an unmitigated order block or FVG in the direction of your bias), checking whether that structural zone's location also falls within the OTE-defined Fibonacci range adds one additional, quantified layer of confluence — similar in function to how the earlier RSI divergence post recommended using that indicator as additional confluence layered onto, rather than replacing, genuine structural analysis.
Why the OTE Concept's Specific Numerical Boundaries Deserve the Same Testing Discipline as Any Other Specific Claim
Similar to the Silver Bullet's precise time-window claim covered in the previous post, OTE's specific 61.8%-79% boundary deserves genuine backtesting against your own data rather than uncritical acceptance — the specific boundary values may deserve slight adjustment for your particular pairs and timeframes based on what your own tested data actually shows, rather than treating the commonly-cited figures as universally, precisely correct without verification.
The Underlying Point
OTE represents a more specific, Fibonacci-quantified extension of the premium/discount framework already covered throughout this series, most valuable as an additional confluence layer narrowing entry precision within an already structurally-confirmed setup, rather than as a standalone signal — and, like the Silver Bullet concept, its specific numerical claims deserve the same genuine, out-of-sample testing this series has recommended applying to any precisely-defined trading concept before full adoption.
Optimal Trade Entry, commonly abbreviated OTE, describes a specific retracement zone — typically the area between the 61.8% and 79% Fibonacci retracement levels of a recent impulsive move — treated as the preferred entry area within the broader SMC framework, directly connecting to and extending the earlier Fibonacci mistakes post covered in this series.
Why This Specific Zone, Rather Than Any Single Fibonacci Level
Connecting directly to the earlier Fibonacci discussion, which noted the 61.8% level's rough alignment with SMC-relevant order block and discount/premium zones, OTE extends this into a defined range rather than a single precise level, on the reasoning that genuine institutional order block zones don't always sit at one exact Fibonacci ratio, but tend to cluster within this broader 61.8%-79% band across a large sample of genuine setups.
How This Connects Directly to the Premium/Discount Framework Covered Earlier
The OTE zone, sitting well within the deeper retracement portion of a move, generally corresponds to genuine discount territory (for a bullish setup) or premium territory (for a bearish setup) as covered in the earlier premium/discount post — meaning OTE is, in substance, a more specific, Fibonacci-quantified version of the same "enter in discount for longs, premium for shorts" principle already covered throughout this series, rather than an entirely separate, competing concept.
Why Combining OTE With Genuine Structural Confirmation Matters
Consistent with the earlier Fibonacci mistakes post's core caution, entering purely because price has reached the OTE zone, without the accompanying structural confirmation (a genuine order block or FVG within that zone, a lower-timeframe CHOCH confirming the retracement has concluded) risks exactly the standalone-Fibonacci-signal problem that post warned against — OTE should function as a refinement narrowing where within an already-identified structural zone your entry sits, not as an independent trigger replacing the structural confirmation this series has emphasized throughout.
A Practical Way to Use OTE Within the Broader Framework Already Covered
After identifying a genuine structural setup (a liquidity sweep, a confirmed CHOCH, an unmitigated order block or FVG in the direction of your bias), checking whether that structural zone's location also falls within the OTE-defined Fibonacci range adds one additional, quantified layer of confluence — similar in function to how the earlier RSI divergence post recommended using that indicator as additional confluence layered onto, rather than replacing, genuine structural analysis.
Why the OTE Concept's Specific Numerical Boundaries Deserve the Same Testing Discipline as Any Other Specific Claim
Similar to the Silver Bullet's precise time-window claim covered in the previous post, OTE's specific 61.8%-79% boundary deserves genuine backtesting against your own data rather than uncritical acceptance — the specific boundary values may deserve slight adjustment for your particular pairs and timeframes based on what your own tested data actually shows, rather than treating the commonly-cited figures as universally, precisely correct without verification.
The Underlying Point
OTE represents a more specific, Fibonacci-quantified extension of the premium/discount framework already covered throughout this series, most valuable as an additional confluence layer narrowing entry precision within an already structurally-confirmed setup, rather than as a standalone signal — and, like the Silver Bullet concept, its specific numerical claims deserve the same genuine, out-of-sample testing this series has recommended applying to any precisely-defined trading concept before full adoption.
- Attachments
-
- diagram.png (19.83 KiB) Viewed 84 times
It’s Fairman 
Re: Free SMC Trading Setups
Old High/Old Low: Why "Old" Liquidity Behaves Differently
Throughout this series, liquidity pools have been discussed extensively — equal highs/lows, session extremes, external versus internal liquidity — but the specific concept of "old" versus "fresh" liquidity, and how age specifically affects a level's reliability, deserves its own direct, dedicated treatment.
What Distinguishes "Old" From "Fresh" Liquidity
A fresh liquidity pool is one that formed recently and hasn't yet been tested or approached again — the resting orders behind it are presumed to still be largely intact. An old liquidity pool is one that formed further in the past, and critically, may have already been partially tested, approached, or eroded by intervening price action, even if it was never technically, fully swept — connecting directly to the earlier order blocks post's discussion of zones degrading with repeated touches, but applied specifically to liquidity pools rather than order block zones.
Why Age Alone Doesn't Automatically Weaken a Level, But Often Correlates With Weakening
An old high or low that has never been approached or tested since it originally formed can actually still hold considerable, largely intact liquidity — age alone isn't the direct mechanism of weakening; what matters is how much intervening price action has occurred near that level, which often, but not always, correlates with the level's age. A very old level that price has simply never come back near retains its original significance largely intact, while a comparatively more recent level that's already been approached and partially tested multiple times may carry weaker remaining liquidity despite its more recent formation.
A Practical Way to Assess a Given Level's Genuine Remaining Significance
Rather than relying purely on age as a proxy, directly check how many times price has approached or interacted with a specific level since it formed, following the same repeated-touch degradation logic covered in the earlier order blocks post — a level approached and rejected from multiple times carries weaker remaining liquidity than an identical-looking level of similar age that's never been retested, regardless of how their raw ages compare to each other.
Why Genuinely Old, Untested Levels Can Offer Particularly Strong Setups
A liquidity pool that's remained completely untouched for an extended period, while price has moved and developed considerably elsewhere, often represents a particularly large, undisturbed pool of resting orders — when price eventually does return to such a level, the resulting reaction can be disproportionately strong compared to a more recently and more frequently tested level, precisely because so little of the original liquidity has been eroded by any intervening activity.
Practical Application for Building Your Watchlist
When reviewing higher-timeframe charts for potential zones of interest (per the earlier pre-market watchlist and HTF POI discussions), specifically flag genuinely old, untested levels alongside more recent ones — these older, undisturbed levels deserve particular attention precisely because their age, combined with their untested status, suggests a potentially larger, more intact liquidity pool than a superficially similar but more recently and repeatedly tested level would offer.
The Underlying Point
A liquidity level's age matters less directly than how much genuine intervening price interaction it's experienced since forming — an old but genuinely untested level can carry disproportionately strong significance precisely due to its undisturbed status, while a more recent but repeatedly-tested level may already carry weakened, degraded significance despite its more recent formation, making direct interaction history, rather than raw age alone, the more reliable diagnostic this series has emphasized throughout its discussion of zone degradation.
Throughout this series, liquidity pools have been discussed extensively — equal highs/lows, session extremes, external versus internal liquidity — but the specific concept of "old" versus "fresh" liquidity, and how age specifically affects a level's reliability, deserves its own direct, dedicated treatment.
What Distinguishes "Old" From "Fresh" Liquidity
A fresh liquidity pool is one that formed recently and hasn't yet been tested or approached again — the resting orders behind it are presumed to still be largely intact. An old liquidity pool is one that formed further in the past, and critically, may have already been partially tested, approached, or eroded by intervening price action, even if it was never technically, fully swept — connecting directly to the earlier order blocks post's discussion of zones degrading with repeated touches, but applied specifically to liquidity pools rather than order block zones.
Why Age Alone Doesn't Automatically Weaken a Level, But Often Correlates With Weakening
An old high or low that has never been approached or tested since it originally formed can actually still hold considerable, largely intact liquidity — age alone isn't the direct mechanism of weakening; what matters is how much intervening price action has occurred near that level, which often, but not always, correlates with the level's age. A very old level that price has simply never come back near retains its original significance largely intact, while a comparatively more recent level that's already been approached and partially tested multiple times may carry weaker remaining liquidity despite its more recent formation.
A Practical Way to Assess a Given Level's Genuine Remaining Significance
Rather than relying purely on age as a proxy, directly check how many times price has approached or interacted with a specific level since it formed, following the same repeated-touch degradation logic covered in the earlier order blocks post — a level approached and rejected from multiple times carries weaker remaining liquidity than an identical-looking level of similar age that's never been retested, regardless of how their raw ages compare to each other.
Why Genuinely Old, Untested Levels Can Offer Particularly Strong Setups
A liquidity pool that's remained completely untouched for an extended period, while price has moved and developed considerably elsewhere, often represents a particularly large, undisturbed pool of resting orders — when price eventually does return to such a level, the resulting reaction can be disproportionately strong compared to a more recently and more frequently tested level, precisely because so little of the original liquidity has been eroded by any intervening activity.
Practical Application for Building Your Watchlist
When reviewing higher-timeframe charts for potential zones of interest (per the earlier pre-market watchlist and HTF POI discussions), specifically flag genuinely old, untested levels alongside more recent ones — these older, undisturbed levels deserve particular attention precisely because their age, combined with their untested status, suggests a potentially larger, more intact liquidity pool than a superficially similar but more recently and repeatedly tested level would offer.
The Underlying Point
A liquidity level's age matters less directly than how much genuine intervening price interaction it's experienced since forming — an old but genuinely untested level can carry disproportionately strong significance precisely due to its undisturbed status, while a more recent but repeatedly-tested level may already carry weakened, degraded significance despite its more recent formation, making direct interaction history, rather than raw age alone, the more reliable diagnostic this series has emphasized throughout its discussion of zone degradation.
- Attachments
-
- diagram.png (17.87 KiB) Viewed 84 times
It’s Fairman
Re: Free SMC Trading Setups
The Unicorn Model: Combining Breaker Blocks and FVGs
The Unicorn Model, a specific, named setup within the broader ICT-influenced SMC vocabulary, describes a particular confluence pattern combining two concepts already covered separately throughout this series — breaker blocks and Fair Value Gaps — worth understanding as a concrete example of how the individual concepts this series has built throughout can combine into more specific, higher-confluence setups.
What the Unicorn Model Specifically Requires
The setup requires a breaker block (per the earlier order blocks post's discussion of a failed order block that flips polarity) and an FVG (per the earlier FVG post) to overlap at the same price zone — the theory being that a zone offering both types of confirming evidence simultaneously represents a particularly strong, high-confluence area of interest, considerably more reliable than either concept appearing in isolation.
Why This Overlap Might Genuinely Represent Stronger Confluence
Connecting directly to the confluence checklist principle covered early in this series, a zone where two independently-derived pieces of structural evidence (a breaker block's polarity-flip significance and an FVG's imbalance-based significance) happen to coincide at the same price level offers a more genuinely convergent signal than either piece of evidence alone — similar in spirit to how the earlier RSI divergence and displacement discussions recommended looking for multiple, independent confirming signals rather than relying on any single piece of evidence in isolation.
How to Practically Identify a Unicorn Setup on Your Own Charts
After identifying a breaker block (following the earlier order blocks post's specific criteria for recognizing a failed order block that's flipped polarity), check whether an FVG from the same or a closely related price move overlaps with that same zone — if it does, you've identified a Unicorn-model setup; if the two concepts are present but don't actually overlap at the same price level, you have two separate, independent pieces of evidence rather than the specific, converged confluence this named setup describes.
Why Naming This Specific Combination Has Genuine Practical Value
Similar to how the Judas Swing concept covered earlier in this series gave a specific, memorable name to reinforce a particular discipline (suspicion of the initial London-open move), giving this specific two-concept overlap its own name makes it easier to specifically watch for and recognize in real time, rather than relying on a more general, unstructured sense that "there's some confluence here" without a specific, defined pattern to check against.
A Reasonable Caution About Overweighting Any Single Named Pattern
Consistent with this series' broader approach to specific, named setups (the Silver Bullet, OTE), the Unicorn Model deserves the same backtesting verification before being treated as a uniquely superior setup — while the underlying logic (convergent, independent confirming evidence) is genuinely sound, per the confluence principle this series has emphasized throughout, the specific claim that this particular two-concept combination is meaningfully superior to other forms of multi-factor confluence deserves testing against your own data rather than uncritical acceptance based on the name and its associated specific-sounding definition alone.
The Underlying Point
The Unicorn Model offers a concrete, well-defined example of the general confluence principle this series has emphasized throughout — specifically requiring convergence between two already-covered structural concepts (breaker blocks and FVGs) at the same price zone — genuinely worth watching for as a specific, named pattern, while still deserving the same honest backtesting scrutiny this series has recommended for any specific, named setup before treating it as uniquely or reliably superior to other forms of multi-factor confluence.
The Unicorn Model, a specific, named setup within the broader ICT-influenced SMC vocabulary, describes a particular confluence pattern combining two concepts already covered separately throughout this series — breaker blocks and Fair Value Gaps — worth understanding as a concrete example of how the individual concepts this series has built throughout can combine into more specific, higher-confluence setups.
What the Unicorn Model Specifically Requires
The setup requires a breaker block (per the earlier order blocks post's discussion of a failed order block that flips polarity) and an FVG (per the earlier FVG post) to overlap at the same price zone — the theory being that a zone offering both types of confirming evidence simultaneously represents a particularly strong, high-confluence area of interest, considerably more reliable than either concept appearing in isolation.
Why This Overlap Might Genuinely Represent Stronger Confluence
Connecting directly to the confluence checklist principle covered early in this series, a zone where two independently-derived pieces of structural evidence (a breaker block's polarity-flip significance and an FVG's imbalance-based significance) happen to coincide at the same price level offers a more genuinely convergent signal than either piece of evidence alone — similar in spirit to how the earlier RSI divergence and displacement discussions recommended looking for multiple, independent confirming signals rather than relying on any single piece of evidence in isolation.
How to Practically Identify a Unicorn Setup on Your Own Charts
After identifying a breaker block (following the earlier order blocks post's specific criteria for recognizing a failed order block that's flipped polarity), check whether an FVG from the same or a closely related price move overlaps with that same zone — if it does, you've identified a Unicorn-model setup; if the two concepts are present but don't actually overlap at the same price level, you have two separate, independent pieces of evidence rather than the specific, converged confluence this named setup describes.
Why Naming This Specific Combination Has Genuine Practical Value
Similar to how the Judas Swing concept covered earlier in this series gave a specific, memorable name to reinforce a particular discipline (suspicion of the initial London-open move), giving this specific two-concept overlap its own name makes it easier to specifically watch for and recognize in real time, rather than relying on a more general, unstructured sense that "there's some confluence here" without a specific, defined pattern to check against.
A Reasonable Caution About Overweighting Any Single Named Pattern
Consistent with this series' broader approach to specific, named setups (the Silver Bullet, OTE), the Unicorn Model deserves the same backtesting verification before being treated as a uniquely superior setup — while the underlying logic (convergent, independent confirming evidence) is genuinely sound, per the confluence principle this series has emphasized throughout, the specific claim that this particular two-concept combination is meaningfully superior to other forms of multi-factor confluence deserves testing against your own data rather than uncritical acceptance based on the name and its associated specific-sounding definition alone.
The Underlying Point
The Unicorn Model offers a concrete, well-defined example of the general confluence principle this series has emphasized throughout — specifically requiring convergence between two already-covered structural concepts (breaker blocks and FVGs) at the same price zone — genuinely worth watching for as a specific, named pattern, while still deserving the same honest backtesting scrutiny this series has recommended for any specific, named setup before treating it as uniquely or reliably superior to other forms of multi-factor confluence.
- Attachments
-
- diagram.png (17.05 KiB) Viewed 84 times
It’s Fairman
Re: Free SMC Trading Setups
The Asian Session Breakout Strategy (When Range Trading Isn't Enough)
This series has extensively covered the Asian range as a liquidity pool to be swept during the London open — but on certain days, the Asian session itself produces a genuine, tradeable breakout rather than simply setting up a later sweep, and recognizing when this alternative pattern is unfolding deserves its own dedicated treatment.
Why the Standard Asian-Range-Sweep Framework Doesn't Apply Every Day
The extensive Asian range and GBPJPY-specific discussions covered earlier in this series assumed a genuinely quiet, consolidating Asian session — but on days with a genuine Asian-session catalyst (a significant AUD, NZD, or JPY-specific data release, per the earlier AUDUSD, NZDUSD, and USDJPY posts, or a significant regional development), the Asian session itself can produce a genuine, sustained directional breakout rather than the tight consolidation the standard sweep framework depends on.
How to Recognize a Genuine Asian Breakout in Progress
Connecting to the earlier stop-hunt-versus-genuine-breakout discussion, a genuine Asian breakout shows the same distinguishing characteristics covered in that post — sustained acceptance beyond the initial range with genuine follow-through and displacement (per the earlier displacement post), rather than a brief spike that quickly reverses. If Asian session price action shows a decisive break of its own early range with continued, accepted movement beyond it, rather than a return back inside, the standard "wait for London to sweep the Asian range" framework may not be the most relevant pattern unfolding that particular day.
Adapting Your Approach When a Genuine Asian Breakout Is Identified
Rather than waiting for a London-session sweep of a range that's already genuinely broken and moved on, apply the trend continuation framework covered earlier in this series to the Asian session breakout itself — treating the breakout's origin as a potential order block or FVG zone for a continuation entry on any retracement, similar to how any other genuine, displacement-confirmed breakout would be approached throughout this series' broader framework.
Why Checking the Asian-Session Calendar Specifically Matters Here
Given that this alternative pattern is specifically triggered by genuine Asian-session catalysts, checking for scheduled AUD, NZD, and JPY-specific releases (per the earlier pair-specific posts) during your pre-session preparation helps anticipate which pattern — the standard range-and-sweep or the alternative genuine-breakout — is more likely to unfold on a given day, rather than defaulting to the same range-sweep expectation regardless of whether a genuine catalyst is scheduled.
Why Misapplying the Standard Range-Sweep Framework to a Genuine Breakout Day Costs Real Money
A trader who assumes every Asian session will consolidate and specifically waits for a London-session sweep, on a day when the Asian session has already produced a genuine, displacement-confirmed breakout, risks either missing a genuine continuation opportunity entirely or, worse, mistakenly trading a countertrend "sweep" setup against a breakout that has no actual intention of reversing — directly connecting to the earlier stop-hunt-versus-breakout discussion's core caution about correctly distinguishing these two genuinely different patterns before committing to a trade.
The Underlying Point
The Asian range framework covered extensively throughout this series applies specifically to genuinely quiet, consolidating Asian sessions — on days with a genuine Asian-specific catalyst, a different, breakout-continuation pattern can unfold instead, and correctly distinguishing which pattern is actually in progress, using the same displacement and acceptance criteria covered throughout this series, matters considerably more than defaulting to a single expected pattern regardless of the day's actual underlying catalyst calendar.
This series has extensively covered the Asian range as a liquidity pool to be swept during the London open — but on certain days, the Asian session itself produces a genuine, tradeable breakout rather than simply setting up a later sweep, and recognizing when this alternative pattern is unfolding deserves its own dedicated treatment.
Why the Standard Asian-Range-Sweep Framework Doesn't Apply Every Day
The extensive Asian range and GBPJPY-specific discussions covered earlier in this series assumed a genuinely quiet, consolidating Asian session — but on days with a genuine Asian-session catalyst (a significant AUD, NZD, or JPY-specific data release, per the earlier AUDUSD, NZDUSD, and USDJPY posts, or a significant regional development), the Asian session itself can produce a genuine, sustained directional breakout rather than the tight consolidation the standard sweep framework depends on.
How to Recognize a Genuine Asian Breakout in Progress
Connecting to the earlier stop-hunt-versus-genuine-breakout discussion, a genuine Asian breakout shows the same distinguishing characteristics covered in that post — sustained acceptance beyond the initial range with genuine follow-through and displacement (per the earlier displacement post), rather than a brief spike that quickly reverses. If Asian session price action shows a decisive break of its own early range with continued, accepted movement beyond it, rather than a return back inside, the standard "wait for London to sweep the Asian range" framework may not be the most relevant pattern unfolding that particular day.
Adapting Your Approach When a Genuine Asian Breakout Is Identified
Rather than waiting for a London-session sweep of a range that's already genuinely broken and moved on, apply the trend continuation framework covered earlier in this series to the Asian session breakout itself — treating the breakout's origin as a potential order block or FVG zone for a continuation entry on any retracement, similar to how any other genuine, displacement-confirmed breakout would be approached throughout this series' broader framework.
Why Checking the Asian-Session Calendar Specifically Matters Here
Given that this alternative pattern is specifically triggered by genuine Asian-session catalysts, checking for scheduled AUD, NZD, and JPY-specific releases (per the earlier pair-specific posts) during your pre-session preparation helps anticipate which pattern — the standard range-and-sweep or the alternative genuine-breakout — is more likely to unfold on a given day, rather than defaulting to the same range-sweep expectation regardless of whether a genuine catalyst is scheduled.
Why Misapplying the Standard Range-Sweep Framework to a Genuine Breakout Day Costs Real Money
A trader who assumes every Asian session will consolidate and specifically waits for a London-session sweep, on a day when the Asian session has already produced a genuine, displacement-confirmed breakout, risks either missing a genuine continuation opportunity entirely or, worse, mistakenly trading a countertrend "sweep" setup against a breakout that has no actual intention of reversing — directly connecting to the earlier stop-hunt-versus-breakout discussion's core caution about correctly distinguishing these two genuinely different patterns before committing to a trade.
The Underlying Point
The Asian range framework covered extensively throughout this series applies specifically to genuinely quiet, consolidating Asian sessions — on days with a genuine Asian-specific catalyst, a different, breakout-continuation pattern can unfold instead, and correctly distinguishing which pattern is actually in progress, using the same displacement and acceptance criteria covered throughout this series, matters considerably more than defaulting to a single expected pattern regardless of the day's actual underlying catalyst calendar.
- Attachments
-
- diagram.png (16.77 KiB) Viewed 84 times
It’s Fairman
Re: Free SMC Trading Setups
Daily, Weekly, and Monthly Liquidity: A Layered Framework
Throughout this series, liquidity concepts have been discussed at various individual timeframes — session ranges, the weekly close, the old-versus-fresh liquidity discussion earlier in this batch — this post ties these threads together into a single, deliberately layered framework for organizing liquidity awareness across multiple timeframes simultaneously.
Why Organizing Liquidity by Timeframe Layer Provides More Clarity Than Treating It as a Single, Undifferentiated Concept
Given how extensively this series has covered liquidity at different scales — session highs/lows, daily extremes, the weekly close discussion, and the earlier HTF-imbalance and weekly-FVG posts — a trader benefits from a deliberate, organized mental structure distinguishing which specific timeframe a given liquidity pool belongs to, rather than treating every identified pool as equivalent regardless of its underlying scale.
The Daily Layer
Daily highs and lows, along with the daily range-used-so-far check covered earlier in this series, represent the most immediately relevant liquidity layer for a scalper's day-to-day execution — these levels update constantly and directly inform the session-level analysis (London open sweeps, NY session patterns) this series has centered on throughout as the primary, moment-to-moment analytical layer.
The Weekly Layer
The weekly high/low and weekly close (per the earlier weekly candle close post) represent a considerably less frequently updating, higher-conviction layer — significant enough to inform overall weekly bias per the multi-timeframe framework, but not something requiring constant, moment-to-moment monitoring the way daily levels do. A weekly high or low being approached carries meaningfully more significance than an equivalent daily-only level, given the greater aggregated conviction behind it.
The Monthly Layer
Monthly extremes represent the least frequently updating, highest-conviction layer within this three-tier framework — connecting to the quarterly theory discussion covered earlier, monthly liquidity pools are approached relatively rarely, and when price does genuinely approach a significant, unmitigated monthly high or low, the resulting reaction (or genuine breakout) tends to carry considerably more weight than the same visual pattern occurring at a purely daily or weekly level.
A Practical Routine for Incorporating All Three Layers Without Overcomplicating Daily Execution
Rather than checking all three layers with equal frequency, a reasonable routine checks daily levels constantly (as the primary, active execution layer), weekly levels during the periodic weekly review already recommended earlier in this series (alongside the weekly close and weekly FVG checks), and monthly levels even less frequently — perhaps monthly or when a genuinely significant, extended move suggests price may be approaching a monthly-scale extreme worth specifically verifying.
Why a Confluence Across Multiple Layers Simultaneously Represents Particularly Strong Setups
Similar to the Unicorn Model's confluence-through-overlap logic covered earlier in this batch, a price level that happens to represent significant liquidity across multiple timeframe layers simultaneously — a daily high that also happens to align closely with an unmitigated weekly or monthly extreme — represents a particularly strong, high-conviction zone, offering more layered confirmation than a level significant on only a single timeframe layer alone.
The Underlying Point
Organizing liquidity awareness into distinct daily, weekly, and monthly layers, each checked at an appropriately different frequency and weighted with appropriately different conviction, provides a more genuinely useful, structured framework than treating every identified liquidity pool as equivalent regardless of its underlying timeframe scale — with particular attention warranted when significant levels across multiple layers happen to converge at the same price zone.
Throughout this series, liquidity concepts have been discussed at various individual timeframes — session ranges, the weekly close, the old-versus-fresh liquidity discussion earlier in this batch — this post ties these threads together into a single, deliberately layered framework for organizing liquidity awareness across multiple timeframes simultaneously.
Why Organizing Liquidity by Timeframe Layer Provides More Clarity Than Treating It as a Single, Undifferentiated Concept
Given how extensively this series has covered liquidity at different scales — session highs/lows, daily extremes, the weekly close discussion, and the earlier HTF-imbalance and weekly-FVG posts — a trader benefits from a deliberate, organized mental structure distinguishing which specific timeframe a given liquidity pool belongs to, rather than treating every identified pool as equivalent regardless of its underlying scale.
The Daily Layer
Daily highs and lows, along with the daily range-used-so-far check covered earlier in this series, represent the most immediately relevant liquidity layer for a scalper's day-to-day execution — these levels update constantly and directly inform the session-level analysis (London open sweeps, NY session patterns) this series has centered on throughout as the primary, moment-to-moment analytical layer.
The Weekly Layer
The weekly high/low and weekly close (per the earlier weekly candle close post) represent a considerably less frequently updating, higher-conviction layer — significant enough to inform overall weekly bias per the multi-timeframe framework, but not something requiring constant, moment-to-moment monitoring the way daily levels do. A weekly high or low being approached carries meaningfully more significance than an equivalent daily-only level, given the greater aggregated conviction behind it.
The Monthly Layer
Monthly extremes represent the least frequently updating, highest-conviction layer within this three-tier framework — connecting to the quarterly theory discussion covered earlier, monthly liquidity pools are approached relatively rarely, and when price does genuinely approach a significant, unmitigated monthly high or low, the resulting reaction (or genuine breakout) tends to carry considerably more weight than the same visual pattern occurring at a purely daily or weekly level.
A Practical Routine for Incorporating All Three Layers Without Overcomplicating Daily Execution
Rather than checking all three layers with equal frequency, a reasonable routine checks daily levels constantly (as the primary, active execution layer), weekly levels during the periodic weekly review already recommended earlier in this series (alongside the weekly close and weekly FVG checks), and monthly levels even less frequently — perhaps monthly or when a genuinely significant, extended move suggests price may be approaching a monthly-scale extreme worth specifically verifying.
Why a Confluence Across Multiple Layers Simultaneously Represents Particularly Strong Setups
Similar to the Unicorn Model's confluence-through-overlap logic covered earlier in this batch, a price level that happens to represent significant liquidity across multiple timeframe layers simultaneously — a daily high that also happens to align closely with an unmitigated weekly or monthly extreme — represents a particularly strong, high-conviction zone, offering more layered confirmation than a level significant on only a single timeframe layer alone.
The Underlying Point
Organizing liquidity awareness into distinct daily, weekly, and monthly layers, each checked at an appropriately different frequency and weighted with appropriately different conviction, provides a more genuinely useful, structured framework than treating every identified liquidity pool as equivalent regardless of its underlying timeframe scale — with particular attention warranted when significant levels across multiple layers happen to converge at the same price zone.
- Attachments
-
- diagram.png (15.23 KiB) Viewed 84 times
It’s Fairman
Re: Free SMC Trading Setups
Hi Fairman,Fairman wrote: Mon Sep 21, 2026 8:20 pm The Silver Bullet Setup: A Specific ICT-Style Time Window Strategy
Among the more specific, narrowly-defined setups circulating in advanced SMC and ICT-adjacent content, the Silver Bullet stands out for its unusually precise time-window definition — worth understanding directly given how specific and testable this particular concept is compared to some of the broader frameworks covered earlier in this series.
What the Silver Bullet Setup Specifically Defines
The setup identifies specific, narrow one-hour windows — commonly cited as roughly 10:00-11:00 AM New York time, and a similar window around the London open — during which a specific sequence is expected: a liquidity sweep (of a recent swing high or low) followed by a market structure shift and a retracement into an FVG or order block left by that shift, with entry taken on that retracement, all expected to complete and resolve within the single defined hour.
Why the Narrow Time Window Is the Defining, Distinguishing Feature
Unlike the broader session-based frameworks covered throughout this series (the full London open discussion, the NY session liquidity sweep post), the Silver Bullet's specific value proposition is its narrow, precisely bounded window — the claim is that this specific hour offers a disproportionately clean, reliable version of the liquidity-sweep-into-reversal pattern this series has covered extensively, compared to the same pattern's reliability across the broader session more generally.
Why This Narrow Specificity Makes the Concept Genuinely Testable
Connecting directly to the backtesting discipline covered throughout this series, the Silver Bullet's precise time-window definition makes it considerably easier to rigorously test than some of the broader, more qualitatively-defined concepts covered elsewhere (quarterly theory, IPDA) — a trader can specifically isolate trades occurring within this defined window and directly compare their performance against similar setups occurring outside it, providing a genuinely clear, quantifiable answer about whether this specific window offers the claimed edge for their own particular pairs and conditions.
A Reasonable, Skeptical Approach to Adopting This Specific Concept
Rather than assuming the claimed edge transfers automatically, apply the same rigorous, bar-by-bar backtesting process covered earlier in this series specifically to this narrow window, comparing setups within it against otherwise-similar setups occurring at other times — if your own data genuinely supports an edge specific to this window, it's a valuable, precisely-defined addition to your trading routine; if it doesn't, the broader session-based framework already covered throughout this series remains a perfectly sound foundation without this specific additional refinement.
Why Precise Time-Window Claims Deserve Extra Scrutiny
Given how many possible narrow time windows could be tested after the fact, and the genuine risk of over-fitting covered in the earlier over-optimization discussion, a specific, narrow time-window claim deserves particular skepticism until verified against a genuinely large, out-of-sample dataset — the same robustness-testing principles covered in the earlier curve-fitting post apply directly here, perhaps with even more weight given how easy it would be for a narrow window like this to have been identified through exactly the kind of after-the-fact historical fitting that post warned against.
The Underlying Point
The Silver Bullet setup offers a genuinely specific, testable refinement of the broader liquidity-sweep framework this series has covered throughout — its narrow, precise definition makes it easier to rigorously verify than several of the more qualitative concepts discussed elsewhere, but that same specificity also means it deserves the same careful, skeptical, out-of-sample testing this series has recommended for any narrowly-defined claim before being adopted as a core part of your trading routine.
thank you very much for your post.
This is a spot-on assessment of why the Silver Bullet setup holds so much appeal compared to broader SMC concepts. You’ve hit exactly on the core tradeoff of quantitative trading: specificity breeds testability, but it also breeds curve-fitting.
When a strategy tells you to look for a generic "liquidity sweep," it leaves too much room for hindsight bias. The trader can easily point to any random wick on a chart and say, "There's the sweep." But when the strategy binds that action to a rigid 60-minute window (10:00–11:00 AM NY time), it strips away the psychological safety net. Either the setup formed inside that hour, or it didn't.
As you noted, this exact specificity is what allows us to apply rigorous, bar-by-bar backtesting. If the 10:00 AM volatility injection genuinely provides a statistical edge in forming sweeps into Fair Value Gaps (FVGs), the data will show it. If it’s just the result of optimization bias by online gurus, the data will expose that too.
To help you actually test these claims out of sample, here is a Pine Script (v5) designed to isolate this exact framework.
Preserve your own money. Scale with the market's money. Exponential growth is the ultimate key.
Re: Free SMC Trading Setups
ICT Silver Bullet: Time Window & FVG Detector - PineScript
This script highlights the 10:00-11:00 AM NY window on your chart and automatically detects any Fair Value Gaps (FVGs) that form specifically within that window, ignoring the noise from the rest of the day.
This script highlights the 10:00-11:00 AM NY window on your chart and automatically detects any Fair Value Gaps (FVGs) that form specifically within that window, ignoring the noise from the rest of the day.
Code: Select all
//@version=5
indicator("ICT Silver Bullet - Time Window & FVG", overlay=true, max_boxes_count=500)
// --- 1. User Inputs ---
// Default is set to the classic 10:00 AM - 11:00 AM NY time window
sb_time = input.session("1000-1100", title="Silver Bullet Time Window")
tz = input.string("America/New_York", title="Timezone (e.g., America/New_York, Europe/London)")
box_length = input.int(5, title="Extend FVG Boxes (Bars)")
// --- 2. Identify the Time Window ---
// Returns true if the current bar is inside the defined session
in_window = not na(time(timeframe.period, sb_time, tz))
// Highlight the background so the trader can visually isolate the Silver Bullet hour
bgcolor(in_window ? color.new(color.blue, 90) : na, title="Silver Bullet Background")
// --- 3. Fair Value Gap (FVG) Logic ---
// A bullish FVG occurs when the current low is higher than the high two bars ago
bull_fvg = low > high[2] and close[1] > open[1]
// A bearish FVG occurs when the current high is lower than the low two bars ago
bear_fvg = high < low[2] and close[1] < open[1]
// --- 4. Draw Setups ONLY inside the Window ---
if in_window
if bull_fvg
// Draw Bullish FVG
box.new(left=bar_index[2],
top=low,
right=bar_index + box_length,
bottom=high[2],
border_color=color.new(color.green, 50),
bgcolor=color.new(color.green, 85),
text="Bull FVG", text_color=color.new(color.green, 20), text_size=size.tiny)
if bear_fvg
// Draw Bearish FVG
box.new(left=bar_index[2],
top=low[2],
right=bar_index + box_length,
bottom=high,
border_color=color.new(color.red, 50),
bgcolor=color.new(color.red, 85),
text="Bear FVG", text_color=color.new(color.red, 20), text_size=size.tiny)Preserve your own money. Scale with the market's money. Exponential growth is the ultimate key.
Re: Free SMC Trading Setups
How to use this for your robustness testing:
Apply it to a low timeframe: This script works best on the 1m, 3m, or 5m charts, which are the standard timeframes for the Silver Bullet execution.
Scan for the Sequence: The script handles the time boundary and the FVG identification. Your job during backtesting is to manually verify the context—did a liquidity sweep (taking out a recent swing high/low) and a Market Structure Shift (MSS) occur immediately prior to the highlighted FVG?
Compare Out-of-Sample: Change the sb_time input to random hours (like 1300-1400 or 0800-0900) and compare the win rate of the exact same mechanical setup. This will tell you if the 10:00 AM window actually holds a unique edge, or if it's just curve-fit marketing.
Apply it to a low timeframe: This script works best on the 1m, 3m, or 5m charts, which are the standard timeframes for the Silver Bullet execution.
Scan for the Sequence: The script handles the time boundary and the FVG identification. Your job during backtesting is to manually verify the context—did a liquidity sweep (taking out a recent swing high/low) and a Market Structure Shift (MSS) occur immediately prior to the highlighted FVG?
Compare Out-of-Sample: Change the sb_time input to random hours (like 1300-1400 or 0800-0900) and compare the win rate of the exact same mechanical setup. This will tell you if the 10:00 AM window actually holds a unique edge, or if it's just curve-fit marketing.
Preserve your own money. Scale with the market's money. Exponential growth is the ultimate key.
Re: Free SMC Trading Setups
This is the exact right progression. If you are trading pure price action on 1-minute or 5-minute charts, relying on raw market structure—specifically where liquidity is resting at swing highs and lows—is far superior to masking the chart with lagging indicators.
To automate this, we use pivot points (fractals) to define the most recent swing highs (Buy-Side Liquidity) and swing lows (Sell-Side Liquidity).
Here is the updated Pine Script. It draws horizontal dashed lines from the most recent swing highs and lows. When price pierces one of these lines, it turns solid, indicating a liquidity sweep. If an FVG forms inside the Silver Bullet window immediately after that sweep, it tags it as a high-probability setup.
To automate this, we use pivot points (fractals) to define the most recent swing highs (Buy-Side Liquidity) and swing lows (Sell-Side Liquidity).
Here is the updated Pine Script. It draws horizontal dashed lines from the most recent swing highs and lows. When price pierces one of these lines, it turns solid, indicating a liquidity sweep. If an FVG forms inside the Silver Bullet window immediately after that sweep, it tags it as a high-probability setup.
Preserve your own money. Scale with the market's money. Exponential growth is the ultimate key.