SwiftTrend Structure█ OVERVIEW
SwiftTrend Structure is an extended version of the SwiftTrend indicator, designed to provide more reliable trend filtering.
The biggest enhancement over the original version is the introduction of dual trend confirmation. A price crossing of the SwiftTrend line alone is no longer sufficient to change the trend direction. Instead, the move must also be confirmed by a corresponding pivot breakout (BoS/ChoCh).
This approach significantly reduces false trend reversals during ranging markets and noisy price action.
Pivot breakout detection (BoS/ChoCh) is an integral part of the indicator's logic and serves as the confirmation mechanism for trend changes. At the same time, these breakout signals can also be used independently as trade signals based on market structure.
All features of the indicator are fully optional and can be enabled or disabled independently, allowing the tool to be used either as a clean trend filter or as a more comprehensive market structure analysis tool.
█ CONCEPTS
Traditional trend-following indicators often reverse too early during consolidations or too late after a new trend has already developed.
The original SwiftTrend determines trend direction solely by the relationship between price and its dynamic trend line.
SwiftTrend Structure extends this concept by incorporating market structure analysis.
A trend reversal is confirmed only when two conditions are met:
* price breaks the SwiftTrend line,
* the corresponding pivot breakout (BoS/ChoCh) occurs.
After price crosses the trend line, the indicator does not immediately change direction. Instead, it enters a pending state, waiting for additional confirmation.
The pending state ends in one of two ways:
* the required pivot breakout (BoS/ChoCh) confirms the trend reversal,
* or price returns back into the previous trend range, canceling the pending state and keeping the existing trend unchanged.
This mechanism filters out many temporary breaks of the trend line that would otherwise generate false trend reversals.
Besides confirming trend changes, the indicator simultaneously monitors pivot breakouts using two independent pivot lengths.
This allows traders to observe both short-term and longer-term market structure.
BoS/ChoCh signals can also be used independently from the trend confirmation logic, making the indicator useful for discretionary Price Action trading.
█ FEATURES
SwiftTrend
* Average Body Periods – period used to calculate the average candle body size
* Band Multiplier – width of the SwiftTrend band
* Tolerance Multiplier – additional margin used while waiting for trend confirmation
* Uptrend Color
* Downtrend Color
* Show Trend Line
* Fill Shade
* Color Bars
* Highlight Waiting State (bgcolor)
Signals
* Show BOS/ChoCh Signals – displays pivot breakout signals
* Show Only BOS/ChoCh Signals Aligned With Trend – filters signals according to the current trend
* Show Trend Change Labels – displays Buy/Sell labels after confirmed trend changes
BoS/ChoCh Confirmation
* Confirm Trend Change With Pivot Breakout – enables dual trend confirmation
* Pivot Length #1 – first pivot detection period
* Pivot Length #2 – second pivot detection period
* Show Broken Pivot Lines – displays broken pivot levels
* Pivot Line Transparency
Unbroken Pivot Lines
* Show Unbroken Pivot Lines – displays active unbroken pivot levels
* Unbroken Pivot Lines Transparency
* Unbroken Pivot Lines Style
TP/SL
* Show TP/SL Levels – displays entry, Stop Loss and Take Profit levels
* Use ATR × For SL Instead Of %
* ATR Period For TP/SL
* ATR Multiplier For SL
* Stop Loss %
* Risk/Reward Ratio For TP1
* Risk/Reward Ratio For TP2
* Risk/Reward Ratio For TP3
TP/SL Display
Independent visibility control for:
* SL
* TP1
* TP2
* TP3
█ APPLICATIONS
SwiftTrend Structure is designed primarily as a trend filter, rather than a standalone buy/sell signal generator.
Its primary purpose is to identify the market direction with the highest probability of continuation.
For example, if:
* a momentum indicator shows bullish pressure,
* SwiftTrend Structure confirms an uptrend,
* a bullish BoS signal appears,
* and there is no significant resistance above price,
a long position may be considered based on the confluence of multiple independent factors.
The same logic can be applied when looking for short opportunities.
Using two independent pivot lengths allows simultaneous analysis of both short-term and long-term market structure.
The built-in TP/SL module provides an immediate visual risk/reward framework, making trade planning faster and more consistent.
█ NOTES
* Dual trend confirmation significantly reduces false trend reversals, although it may also delay the detection of new trends. This is a deliberate trade-off between faster reactions and higher signal quality.
* Disabling pivot confirmation makes the indicator behave similarly to the original SwiftTrend.
* Every module of the indicator can be enabled or disabled independently.
* BoS/ChoCh signals can be used both as trend confirmation and as standalone market structure signals.
* Best results are achieved when combined with market structure analysis, support and resistance zones, momentum indicators, and additional confirmation tools. Wskaźnik
Context Fibonacci Key LevelsContext Fibonacci Key Levels automatically plots Fibonacci retracement and extension levels using the most recently completed Day, Week and Month candles while preserving the directional context of each timeframe.
Rather than treating every Fibonacci equally, the indicator determines whether the previous higher timeframe candle closed bullish or bearish and automatically adjusts the Fibonacci orientation to reflect that completed price movement.
This creates objective reference levels that remain consistent across every chart timeframe.
Automatic Past Day Fibonacci
Automatic Past Week Fibonacci
Automatic Past Month Fibonacci
Automatic bullish or bearish orientation
Retracement and extension levels
Works on every timeframe
Independent colors for each timeframe
Optional labels:
Full Name or Shorthand display mode
How it works
The indicator evaluates the previous completed candle of each selected higher timeframe.
If the candle closed bullish , the Fibonacci is drawn from Low to High.
If the candle closed bearish , the Fibonacci is drawn from High to Low.
This allows every Fibonacci to represent the completed directional movement of its corresponding candle.
Included Fibonacci Levels
0%
23.6%
38.2%
50%
61.8%
78.6%
100%
Customization
Enable or disable Past Day Fibonacci.
Enable or disable Past Week Fibonacci.
Enable or disable Past Month Fibonacci.
Choose an individual color for each timeframe.
Adjust line width.
Show or hide labels.
Display labels using Full Name (Past Day, Past Week and Past Month) or Shorthand (PD, PW and PM).
Use Cases
These levels can be used as objective higher timeframe reference zones for technical analysis, confluence studies, liquidity mapping, retracement analysis, extension targets and general market structure observations.
Because the calculations are always based on the latest completed higher timeframe candle, the levels automatically update whenever a new Day, Week or Month closes.
Disclaimer
This indicator is designed as a technical analysis tool and does not generate trading signals or predict future market direction. It is intended to be used alongside your own trading methodology and additional sources of market confluence. Wskaźnik
[ A L P H A X ] MAGNET - Liquidity Magnet EngineAlphaX MAGNET — Liquidity Magnet Engine: Hybrid Pool Detection, Sweep State Machine, Delayed Reclaim Entries, Absorption Pins, FVG Confluence & Weighted Scoring System
AlphaX MAGNET is a professional-grade liquidity-based trading system built around a single foundational observation: price is magnetically attracted to liquidity pools. Buy-side liquidity sitting above Equal Highs and sell-side liquidity sitting below Equal Lows are not random price levels — they are concentrations of institutional stop orders and pending market orders that price is consistently drawn toward before major directional moves begin. MAGNET detects these pools with a dual-method engine (pivot cluster analysis combined with Equal High/Equal Low range scanning), tracks every sweep event through a dedicated state machine, and fires precision entries through four distinct setup types — same-bar sweep and reclaim, delayed post-sweep reclaim, absorption pin bar, and FVG-liquidity overlap — scored through a weighted 9-point confluence system that rewards quality setup combinations over arbitrary filter accumulation. Unlike systems that suppress signals through cascading hard blocks, MAGNET is built on the philosophy that quality comes from the combination of setup type and confluence score, not from eliminating signal opportunities through excessive gating. Designed for active traders across crypto, forex, gold, and indices on any timeframe.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
💧 The Liquidity Pool Concept — Why Price Is Magnetic
Retail traders place stop losses at technically logical locations — just below swing lows (buy stops become sell orders when triggered, providing sell-side liquidity or SSL) and just above swing highs (sell stops become buy orders when triggered, providing buy-side liquidity or BSL). These clusters are not secrets. Institutional participants, who need massive liquidity to fill their position sizes, deliberately engineer price moves toward these clusters — hunting the stops to generate the counterparty order flow they need.
This creates a recurring, exploitable pattern:
SSL pools below significant lows are swept — price dips below to trigger sell stops, filling institutional buy orders
The sweep reverses sharply as the institutional position is filled and price moves in the intended direction
BSL pools above significant highs are swept — price spikes above to trigger buy stops, filling institutional sell orders
The spike reverses as the selling position is filled
MAGNET is built to detect these pools before the sweep, identify the sweep the moment it occurs, and provide structured entry signals at the precise points where the institutional reversal is most likely to begin. The word "magnet" captures the system's core thesis: liquidity pools are not just price levels to avoid — they are targets that price is attracted to, and the moment after the sweep is the highest-probability institutional entry available.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔍 The Hybrid Pool Detection Engine
MAGNET identifies liquidity pools using two independent methods running simultaneously, then combines their outputs to determine the single most relevant BSL and SSL level at any moment.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Method 1 — Pivot Cluster Analysis
The first engine detects fractal swing highs and lows using a configurable pivot length (default: 5 bars each side) and tracks clusters of pivots near the same price level. Rather than marking every single pivot as a liquidity level, MAGNET uses a weighted averaging approach:
When a new pivot forms near an existing pivot level (within 1.5× the ATR pool tolerance), the two pivots are merged — the new cluster level is the weighted average of both, and the touch count increments. When a new pivot forms far from the existing cluster, a new level is established.
A pivot cluster only becomes an active liquidity pool when its touch count meets the minimum threshold (default: 2 pivot touches) and its age exceeds the minimum pool age (default: 3 bars). These two conditions ensure the pool represents genuine accumulated stop orders rather than a single swing point that may not yet have attracted meaningful liquidity.
Why pivot clustering matters: A level touched twice or more has drawn retail traders to place stops at it on multiple occasions. Each time price revisits without breaking, more stops accumulate just beyond it. The cluster represents not a single trader's stop but a compounding concentration of stop orders — the largest and most powerful liquidity pools in the market.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Method 2 — Equal High / Equal Low (EQH/EQL) Range Scanning
The second engine scans the entire lookback window (default: 40 bars) to find the highest high and lowest low in the range, then counts how many bars within that window came within the ATR pool tolerance of those extremes. When the touch count meets the minimum EQ touch threshold (default: 2 touches), the extreme qualifies as a genuine Equal High (BSL pool) or Equal Low (SSL pool).
Why EQH/EQL scanning is powerful: The highest level in a range with multiple near-touches is the quintessential Equal Highs pattern — the most widely recognized institutional liquidity target in smart money trading. Every time price approaches but fails to break through the level, another wave of retail traders places buy stops above it "in case it breaks." The more touches, the denser the liquidity cluster above. The EQL range scan identifies these levels objectively and in real time without requiring manual identification.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Pool Selection Logic
From both methods, MAGNET selects the single most relevant active BSL and SSL level at any moment. When both methods have identified a valid pool of the same type, the closer one to the current price is selected — the near-term liquidity target takes precedence over a more distant one. The active pools are displayed on the dashboard as exact prices and plotted as dashed lines extending forward on the chart.
Magnet Above / Magnet Below: The active BSL (if above current price) is displayed as MAGNET ABOVE — the level price is currently being drawn toward on the upside. The active SSL (if below price) is MAGNET BELOW — the downside liquidity target. These two levels are also used as the take-profit targets when TP at Opposing Magnet is enabled, with the opposing pool being the natural delivery target after a sweep reversal.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚡ The Sweep State Machine — Separating Sweeps from Entries
One of MAGNET's most important architectural decisions is the separation of the sweep detection from the entry signal. Many liquidity-based systems fire entries on the sweep bar itself — which frequently catches false sweeps, wicks that briefly cross the pool but are part of a larger continuation move, and cascade waterfall bars that are not genuine reversals.
MAGNET uses a dedicated sweep state machine that tracks every sweep event independently from the entry logic:
Sweep detection:
An SSL sweep is detected when the current bar's low extends below the active SSL pool by more than the minimum sweep depth (default: 0.10× ATR). A BSL sweep is detected when the high extends above the active BSL by more than the minimum depth. Both are registered in memory with the bar index and the exact pool level that was swept.
Sweep window tracking:
After a sweep is registered, the system tracks how many bars have elapsed since the sweep. The configurable reclaim window (default: 8 bars) defines how long a sweep remains "fresh" for delayed reclaim entry qualification. The dashboard's SWEEP WINDOW row displays the active sweep state in real time — "SSL 2b ago" means an SSL sweep occurred 2 bars ago and the reclaim window is still open.
Cascade block (same-bar only):
A "cascade" bar is a strong, large-body continuation bar in the trend direction — close below open, body above 0.45× ATR, closing below the structure EMA and 50 EMA (bear cascade). When a sweep coincides with a cascade bar on the same bar , the same-bar sweep entry (Setup A) is blocked — entering against a waterfall candle in the same bar is the highest-risk stop-hunt entry scenario. Critically, this block only applies to same-bar entries — the cascade does not prevent the delayed reclaim entries (Setup B) that fire on subsequent bars once the cascade has resolved.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🏷 Four Setup Types — Quality Through Combination
MAGNET's philosophy explicitly rejects quality-through-suppression. Rather than applying increasingly aggressive filters that block more and more signals, MAGNET provides four distinct setup types of varying quality, grades them A or B, scores them through the weighted confluence engine, and lets the score threshold determine which signals reach the chart. Each setup type captures a different institutional entry scenario.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Setup A — SSL/BSL Sweep + Same-Bar Reclaim (Grade A, Primary)
The highest-conviction single-bar pattern. Fires when the sweep and the reclaim occur within the same bar — the classic stop-hunt candle.
Long conditions (SSL sweep + reclaim):
Current bar's low extends below the active SSL pool by more than the minimum sweep depth
The bar closes back above the SSL pool — the sweep was rejected within the same candle
A qualifying bull trigger candle is present — close above open, body at least 0.22× ATR, and the close-to-low distance exceeds 50% of total range (strong rejection wick)
The bar is not a cascade/waterfall bar — the same-bar cascade block applies
The institutional sequence: Price spikes below the SSL, triggering retail sell stops and filling institutional buy orders. Buyers immediately overwhelm the sell-stop flow and drive price back above the level within the same bar. This same-bar recovery is the clearest possible sign of genuine institutional absorption — they bought the stop-triggered selling and bid price back up in a single candle.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Setup B — Delayed SSL/BSL Reclaim (Grade A, Primary)
The most powerful setup type for catching genuine post-sweep reversals. Fires in the 1 to N bars following a sweep event — capturing entries that miss the same-bar candle.
Long conditions (delayed SSL reclaim):
A qualifying SSL sweep occurred within the reclaim window (1 to 8 bars ago — the current bar is not the sweep bar)
The current bar's low is within ATR tolerance of the swept SSL level — price has returned to test the swept level
The current bar closes above the swept level — reclaiming it from below
A qualifying bull trigger candle confirms the reclaim with body and wick requirements
Why delayed reclaim is the highest-quality setup: Many genuine institutional sweep-and-reversal sequences do not complete in a single bar. After the sweep candle, price may consolidate below the swept level for 1–3 bars as retail traders interpret the sweep as a genuine breakdown and add to short positions. This consolidation below the swept level creates the highest-quality delayed reclaim entry — buying precisely as the "trapped shorts" below the swept level begin to be squeezed on the reclaim. Entries here have the swept level as a natural structural reference for the stop, the opposing BSL pool as a natural target, and the maximum available momentum from both the original sweep exhaustion and the trapped short squeeze.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Setup C — SSL/BSL Absorption Pin (Grade B, Secondary)
A volume-confirmed pin bar at the pool zone — institutional absorption without a full sweep event.
Long conditions (SSL absorption):
Price is at or near the active SSL zone (within ATR pool tolerance)
A pin bar forms — lower wick exceeds 42% of the bar range, body is less than 38% of range, bar closes bullish
Volume is spiking above the configured volume threshold (default: 1.05× average) — confirming institutional activity at the zone
The bar closes above the SSL level — the absorption is from the buy side
The absorption scenario: Not every institutional accumulation at a liquidity pool involves a dramatic sweep. Sometimes institutions absorb all available sell-side liquidity at the SSL boundary without price needing to fully breach the level — the large volume at the pin bar low represents the same buying activity, just without the stop-triggering violation. The combination of the pin bar rejection shape and the volume spike at the zone is the visual and volumetric evidence of this absorption.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Setup D — FVG + SSL/BSL Magnet Confluence (Grade B, Secondary)
The institutional structure overlap entry — a Fair Value Gap forming directly at the liquidity pool level.
Long conditions (FVG + SSL magnet):
A bullish Fair Value Gap is present on the current bar — the current bar's low is above the high of the bar two bars ago, creating a gap in the price structure
The FVG zone (between the current bar's low and the two-bars-ago high) overlaps with the active SSL pool level within ATR tolerance
A qualifying bull trigger candle confirms
The FVG-liquidity overlap concept: When a bullish FVG coincides with an SSL pool level, two independent institutional frameworks are pointing to the same price zone simultaneously. The FVG represents an imbalance in order flow that price will fill. The SSL pool represents a liquidity concentration that price is magnetically drawn toward. When they overlap at the same level, the zone has double-layer institutional significance — it is both an unfilled order imbalance and a liquidity pool, making it the highest-value structural level available at that moment.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Weighted Confluence Scoring — Quality Through Combination
MAGNET uses a weighted scoring system where primary setups (A and B — sweep and reclaim) count for 2 points while secondary setups (C and D — absorption and FVG) count for 1 point. The remaining 7 points come from confluence quality layers. The default minimum threshold is 5 points.
Score structure (maximum: 9 points):
Setup Type (2 points for primary, 1 for secondary) — the foundational quality weighting. A sweep or delayed reclaim inherently carries more institutional evidence than an absorption or FVG overlap
Active Pool Valid (1 point) — the SSL (for bull) or BSL (for bear) pool is currently active and qualified. Signals without a valid pool cannot score this point — there is no institutional liquidity reference without a qualified pool
HTF Bias Alignment (1 point) — the higher timeframe EMA structure agrees with the signal direction. Unlike most AlphaX systems where HTF is a hard block, MAGNET treats HTF as a soft confluence layer — counter-HTF trades can still fire if other confluence is sufficient. This reflects the reality that sweep-and-reclaim sequences frequently work counter-HTF precisely because institutions are sweeping retail positions that were trading with the HTF trend
Volume Layer (1 point) — current bar volume meets or exceeds the volume spike threshold. Confirms institutional participation on the signal bar
Structural Bias (1 point) — price is above the Structure EMA or RSI is above 45 for longs (close > structure EMA or RSI > 45); price below EMA or RSI < 55 for shorts. This dual condition accepts both trend-aligned and momentum-recovering entries
RSI Exhaustion (1 point) — RSI below 38 for longs with a recent SSL sweep, or RSI above 62 for shorts with a recent BSL sweep. This bonus point rewards entries where the RSI is genuinely oversold or overbought at the sweep level — the classic exhaustion reversal condition that historically produces the sharpest recoveries
Non-Chop Market (1 point) — Choppiness Index below the configured threshold (default: 65). Also enforced as a hard gate — unlike the HTF, extreme chop does block all signals regardless of score
At Pool Zone (1 point) — the current bar is within the pool tolerance of the active SSL (bull) or BSL (bear) zone. Rewards entries that are precisely positioned at the institutional level
Score examples:
A primary sweep reclaim (2 points) with valid pool, HTF alignment, volume, structural bias, and non-chop market reaches 7/9 — a high-conviction signal. A secondary FVG entry (1 point) with valid pool, volume, structural bias, and non-chop but no HTF alignment reaches 5/9 — the minimum threshold. The scoring naturally produces a gradient of signal quality without hard-blocking any combination.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 Magnet-Anchored Stop Loss and Target
Stop Loss Placement:
For bull signals, the stop is placed at the minimum of the current bar's low and the swept SSL level (using the stored sweep level from the state machine when a sweep occurred), minus the configured ATR buffer (default: 1.0× ATR). For bear signals, the maximum of the bar's high and the swept BSL level plus the ATR buffer.
This produces stops anchored to the structural invalidation point — the level that proves the institutional thesis wrong. A bull stop below the swept SSL means: if price closes below the sweep level after the reclaim, the sweep thesis has failed and institutions are not actually buying at this level.
Take Profit — Opposing Magnet (default: on):
When TP at Opposing Magnet is enabled, the take profit target is automatically set to the opposing liquidity pool — the BSL pool above price for long entries, the SSL pool below for shorts. This is the single most powerful TP mechanic available for liquidity-based trading: after a sweep of the SSL, the natural delivery target is the opposing BSL pool, because institutions who bought the SSL sweep will deliver price toward the next concentration of liquidity above. The magnet-to-magnet target represents the true institutional delivery destination.
When no opposing magnet is available (pool not yet qualified), the fallback is a configurable R-multiple target (default: 2.5R).
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Live Dashboard
The 17-row real-time dashboard displays the complete internal state across five sections.
LIQUIDITY
BSL (EQH) — the active buy-side liquidity pool price. The current institutional overhead target. Red dashed line on chart with BSL · EQH label
SSL (EQL) — the active sell-side liquidity pool price. The current institutional downside target. Yellow-green dashed line with SSL · EQL label
Magnet Above — the BSL pool when it is above current price — the upside delivery target
Magnet Below — the SSL pool when below current price — the downside delivery target
SWEEP STATE
Sweep Window — live sweep state: "SSL 2b ago" when within the reclaim window, "BSL 3b ago" for BSL sweeps, or — IDLE when no recent sweep is active. This is the critical pre-signal awareness row — when it shows an active sweep state, Setup B entries are monitoring for the reclaim
SETUPS
Long Setup — the currently active long setup type: SWEEP, RECLAIM, ABSORB, FVG, or — when none is active
Short Setup — the currently active short setup type
FILTERS
HTF Bias — ▲ BULL, ▼ BEAR, or — FLAT. Soft confluence layer for scoring
Chop Index — live Choppiness Index value. Orange when above the block threshold — the only hard filter in MAGNET
CONFLUENCE
Bull / Bear — live scores displayed as "x / y" with a ▲ or ▼ arrow when either score meets the minimum threshold
Playbook — the current actionable state: LONG A, SHORT A, LONG B, SHORT B when a signal just fired; WATCH RECLAIM ▲ or ▼ during active sweep windows; WATCH MAGNETS when pools are defined but no active sweep
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📈 Chart Visual System
BSL Pool Line (red dashed) — the active buy-side liquidity level with "BSL · EQH" label extending to the right. Redrawn on the last bar to reflect the current pool state
SSL Pool Line (yellow-green dashed) — the active sell-side liquidity level with "SSL · EQL" label
▲ Large Triangle (below bar, yellow-green) — Grade A long signal. SSL sweep or delayed reclaim with qualifying confluence
▲ Small Triangle (below bar, dim yellow-green) — Grade B long signal. Absorption pin or FVG magnet setup
▼ Large Triangle (above bar, red) — Grade A short signal
▼ Small Triangle (above bar, dim red) — Grade B short signal
● Sweep Circles (optional, orange) — appear above (BSL sweep) or below (SSL sweep) the bar when a sweep event is detected. Off by default — sweeps are tracked internally regardless of marker visibility
SL Guide (red dotted circles) — sweep-anchored stop loss below or above the pool level
TP Guide (yellow-green dotted circles) — opposing magnet target or R-multiple fallback
Live confluence label — B x · S x near the current price on the last bar, updating in real time
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🚀 How to Trade with AlphaX MAGNET — Step by Step
Step 1 — Read the Liquidity Map
Check the dashboard BSL and SSL rows. These are the current institutional targets — price will be drawn toward both levels over time. Note which is closer to current price
Check Magnet Above and Magnet Below. These are your directional delivery destinations. If SSL is below and BSL is above, the market is sandwiched between two magnets — the next major move will likely target one of them
Note the Chop Index. When it is approaching or above the threshold (65), the liquidity pool targets lose reliability — pools become harder to reach when the market is oscillating without direction
Step 2 — Monitor the Sweep Window
The Sweep Window row is the most critical pre-signal dashboard row. "SSL 1b ago" means an SSL sweep just occurred one bar ago and the reclaim window is wide open — Setup B is actively scanning the next bars for a qualifying reclaim candle
WATCH RECLAIM ▲ in the Playbook row is the highest-priority alert state. Prepare your entry parameters immediately — the delayed reclaim may fire on the very next qualifying bar
Watch the chart for the reclaim candle forming at or above the swept SSL level with a bullish rejection body
Step 3 — Enter on the MAGNET Signal
A large ▲ triangle (Grade A) confirms a sweep or delayed reclaim with qualifying confluence. This is the primary MAGNET entry
A small ▲ triangle (Grade B) confirms an absorption or FVG setup. Valid entry with slightly lower setup-type evidence — manage with smaller size if preferred
The SL guide is plotted below the swept level plus ATR buffer. Your structural invalidation
The TP guide points to the opposing BSL magnet when available — the institutional delivery target. When this lines up with the opposing pool, you have a magnet-to-magnet trade with a clear institutional narrative
Step 4 — Manage the Trade
Monitor the Sweep Window — if a new sweep of the opposing pool occurs while you are in a trade, it may be a signal that the delivery is completing or extending
When price approaches the MAGNET ABOVE level (for long trades), consider taking partial profit — the opposing pool is the target but also potential new resistance
If a new valid sweep of your entry SSL occurs in the opposite direction during the trade, this could indicate the SSL was not the final sweep — reassess the position
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ Identifying Low-Quality Conditions — When Not to Trade
Stand aside when:
Chop Index above threshold — this is the only hard filter in MAGNET. All signals are blocked. More importantly, in extreme chop, liquidity pools are being tested repeatedly without producing clean sweeps and reversals — the institutional dynamic is absent
BSL and SSL are very close to each other — when the two magnets are tightly compressed around current price, the market is ranging within a narrow liquidity cluster. Sweeps in this environment frequently continue through multiple levels rather than reversing at the first pool
Sweep Window shows IDLE for an extended period — no sweeps means no primary setup type is available. Only absorption and FVG setups (Grade B) can fire. If you prefer primary setups only, wait for a sweep to register
HTF Bias strongly opposes the signal — while HTF is a soft confluence layer in MAGNET, a strongly opposing HTF reduces the score by 1 point. In these conditions, a Grade B signal at the minimum threshold becomes marginal — consider requiring a higher score for counter-HTF entries
Grade B signals with minimum score (5/9) in a non-trending market — absorption pins and FVG overlaps require more supporting confluence to be reliable in Balance or transitional markets. When Grade B fires at exactly the minimum score without HTF support, reduce size or skip
Multiple consecutive sweeps of the same level without recovery — when price sweeps the SSL three times in succession, each time recovering only partially before sweeping again, the level is being absorbed in stages by a larger institutional seller rather than being swept for a reversal. Do not continue entering on each successive sweep
The ideal MAGNET setup:
Clear, well-aged SSL or BSL pool with multiple touches (3+ pivots or EQ touches)
Clean, decisive sweep below SSL with a single strong bar
1–3 bar consolidation below the swept level (confirming trapped shorts)
Delayed reclaim candle forming at the swept level with bull trigger confirmation
RSI below 38 at the sweep low (exhaustion bonus point)
Volume spike on the reclaim bar
HTF aligned bullish
Opposing BSL pool clearly defined above — the magnet-to-magnet trade
Score at 8–9/9
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚡ Key Features
💧 Hybrid dual-method pool detection — pivot cluster analysis (weighted average clustering with touch count and age requirements) combined with Equal High/Equal Low range scanning (touch count across lookback window)
🎯 Active pool selection logic — nearest qualified pool to current price is selected as the active target, ensuring the most immediately relevant liquidity level is always the reference
⚡ Dedicated sweep state machine — sweeps are detected and stored independently from entry logic, enabling delayed reclaim entries 1–8 bars after the sweep event with full state persistence
🛡 Cascade block (same-bar only) — waterfall continuation bars are blocked from triggering same-bar sweep entries while preserving all delayed reclaim opportunities
🏷 Four setup types with grade classification — Setup A (same-bar sweep reclaim), Setup B (delayed reclaim), Setup C (absorption pin), Setup D (FVG liquidity overlap), each graded A or B by primary/secondary classification
📊 Weighted confluence scoring — primary setups count 2 points, secondary count 1, with 7 additional quality layers scoring independently. Quality through combination, not suppression
🔴 RSI exhaustion bonus — extra confluence point when RSI is genuinely exhausted at the sweep level, rewarding the highest-quality reversal conditions
📡 HTF bias as soft layer — higher timeframe alignment adds to the score but does not hard-block counter-HTF entries, reflecting the institutional reality that sweep reversals frequently work counter to the prevailing HTF trend
🎯 Opposing magnet TP system — take profit automatically targets the opposing liquidity pool when available, providing an institutionally justified delivery destination rather than an arbitrary ATR multiple
📍 Sweep-anchored SL placement — stop loss anchored to the swept pool level plus buffer, not an arbitrary ATR distance from entry
💹 Live Sweep Window tracking — dashboard shows active sweep state with bars elapsed since sweep, providing pre-signal awareness before the delayed reclaim fires
📊 Live Playbook row — displays WATCH RECLAIM ▲/▼ during active sweep windows, preparing you for the imminent Setup B signal
📊 17-row live dashboard — Liquidity, Sweep State, Setups, Filters, and Confluence sections updated in real time
🔔 4 alert conditions — long/short entries and SSL/BSL sweep events
🎨 Fully cohesive dual-tone color system — yellow-green for SSL/SSL-related bull elements, red for BSL/BSL-related bear elements, orange for sweep markers and alerts
⚙ Fully configurable — pivot length, EQH/EQL lookback, pool tolerance, touch minimums, pool age, sweep depth, reclaim window, signal body minimum, all four setup enables, confluence minimum, HTF timeframe and EMAs, chop threshold, volume filter, session, SL buffer, TP mode and R-multiple, and all colors are independently adjustable
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚙ Settings Reference
Liquidity Pool Engine
Pivot Length — fractal sensitivity for pivot high/low detection (default: 5 bars each side)
EQH/EQL Scan Lookback — bars used for the Equal High/Equal Low range scan (default: 40)
Pool Tolerance (xATR) — ATR multiple defining the zone width around a pool level (default: 0.14)
Min Pivot Touches — minimum pivot cluster touches for a pivot pool to qualify (default: 2)
Min EQ Touches — minimum near-touches for an EQH/EQL level to qualify (default: 2)
Min Pool Age (bars) — minimum bars since first pivot detection before the pool is active (default: 3)
ATR Length — ATR calculation lookback (default: 14)
Sweep & Reclaim
Min Sweep Depth (xATR) — minimum extension beyond the pool for a sweep to register (default: 0.10)
Reclaim Window (bars after sweep) — how many bars after a sweep a delayed reclaim can fire (default: 8)
Min Signal Body (xATR) — minimum candle body size for all entry triggers (default: 0.22)
Show Sweep Markers — toggle optional orange circle markers at sweep detection bars (default: off)
Entry Setups
A · SSL Sweep + Reclaim / A · BSL Sweep + Reclaim — toggle same-bar sweep entries
B · Delayed SSL Reclaim / B · Delayed BSL Reclaim — toggle delayed reclaim entries
C · SSL Absorption Pin / C · BSL Absorption Pin — toggle absorption pin bar entries
D · FVG + SSL Magnet / D · FVG + BSL Magnet — toggle FVG-liquidity overlap entries
Min Confluence Score — minimum weighted score required for a signal (default: 5)
Show Entry Signals — toggle signal triangles
Show Confluence Label — toggle the live B/S score label near the current price
Signal Cooldown (bars) — minimum bars between consecutive signals (default: 5)
Grade Signals (A / B) — when on, primary setups show as large triangles, secondary as small triangles
Filters
HTF Bias Layer — adds 1 confluence point when HTF agrees (does not hard-block counter-trend)
HTF Timeframe / HTF Fast / Slow EMA — higher timeframe parameters (defaults: 60-minute / 21 / 55)
Block Extreme Chop — when on, Choppiness Index above threshold blocks all signals (the only hard filter)
Choppiness Length / Chop Block Above — CI parameters (defaults: 14 / 65.0)
Volume Layer — adds 1 confluence point when volume exceeds threshold
Volume Spike Threshold / Volume Avg Length — volume parameters (defaults: 1.05 / 20)
Session Filter / Active Session — trading hours restriction (default: off)
Structure EMA — EMA used for the structural bias confluence layer (default: 21)
Exit Guidance
Show SL / TP Guides — toggle stop and target dotted circle plots
SL Beyond Sweep (xATR) — ATR buffer beyond the swept pool level for stop placement (default: 1.0)
TP at Opposing Magnet — when on, TP targets the opposing active liquidity pool (default: on)
TP Reward (R) if no magnet — fallback R-multiple target when no opposing pool is available (default: 2.5)
Display
Show Liquidity Pool Lines — toggle BSL and SSL dashed reference lines
Show Dashboard — toggle the full dashboard
Dashboard Position — Top Left / Top Right / Bottom Left / Bottom Right
Colors
Bull / Bull Bright — yellow-green family for all bullish signals and SSL elements
Bear / Bear Bright — red family for all bearish signals and BSL elements
Sweep / Alert — orange for sweep markers and active alert states
BSL Pool (EQH) / SSL Pool (EQL) — individual pool line colors
SL Guide / TP Guide — stop and target circle colors
Dash Text / Dash BG / Dash Header / Dash Section / Dash Frame — full dashboard color control
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔔 Alert Conditions (4 total)
Entry Alerts
Magnet Long — all conditions confirmed. Long signal fired across any qualifying setup type
Magnet Short — all conditions confirmed. Short signal fired
Sweep Alerts
Magnet SSL Swept — sell-side liquidity pool has been swept. Watch for reclaim within the configured window — Setup B is now monitoring
Magnet BSL Swept — buy-side liquidity pool has been swept. Watch for reclaim — Setup B monitoring active
All alert messages are formatted as const strings for clean webhook and notification platform integration.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 Recommended Settings by Instrument & Timeframe
The default configuration is optimized for XAUUSD, major forex pairs, and crypto on M5–M15 :
Pivot Length at 5 — standard fractal sensitivity for intraday instruments. Captures meaningful swing points without over-sensitivity to micro-noise
EQL Lookback at 40 — approximately 3–4 hours on M5, covering the relevant intraday Equal High/Low structure
Pool Tolerance at 0.14× ATR — tight enough to require genuine proximity to the pool level without missing valid touches due to spread variation
Reclaim Window at 8 bars — on M5 this is 40 minutes, sufficient to capture post-sweep consolidation and delayed reversal entries
HTF at 60-minute as soft layer — adds score for alignment without blocking the counter-HTF sweeps that are often the most powerful entries
For other instruments or timeframes, adjust:
M1–M3 scalping — reduce Pivot Length to 3, reduce Pool Tolerance to 0.10, reduce Reclaim Window to 4–5 bars, reduce Cooldown to 3, increase Min Sweep Depth to 0.15 for tighter scalp sweeps
H1–H4 swing trading — increase EQL Lookback to 80–100, increase Pivot Length to 7–8, increase Reclaim Window to 12–15, increase TP Reward to 3.5–5.0R for wider swing targets
Crypto (BTC, ETH) — increase Pool Tolerance to 0.18–0.22 for the wider tick structure, increase Min Sweep Depth to 0.15–0.20, increase Chop Block to 68–70 for crypto's naturally higher choppiness
Indices (NAS100, US30) — use session filter for cash market hours, increase Pool Tolerance slightly to 0.16, consider reducing EQL Lookback to 25–30 for the shorter-lived Equal High/Low structures in index futures
More primary setups (A and B) — reduce Reclaim Window minimum expectation by ensuring both Setup A and B are enabled, and watch the Sweep Window row actively rather than waiting for signals
Grade A signals only — disable Setup C (absorption) and Setup D (FVG), raise Min Confluence to 6. Only sweep and delayed reclaim entries with strong supporting factors will fire
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
👥 Who This Is For
💧 Liquidity sweep traders and stop-hunt entry specialists — MAGNET is the most complete and technically sophisticated liquidity sweep system in the AlphaX suite. Every component — pool detection, sweep state machine, cascade blocking, delayed reclaim, magnet TP — is designed specifically for the institutional stop-hunt-and-reverse pattern
🏦 Smart money concepts and ICT methodology traders — the SSL/BSL, EQH/EQL, and sweep-reclaim framework directly implements the core ICT liquidity concepts with quantitative precision
🥇 Gold (XAUUSD) and forex traders — liquidity sweeps are most consistent and most powerful on institutional instruments where market makers actively hunt stops. Default settings are calibrated for gold intraday
🎯 Traders who want the highest-quality post-sweep entries — the delayed reclaim (Setup B) is the system's most powerful setup type and is specifically designed for traders who have experienced the frustration of missing same-bar sweep reversals only to watch price surge without them
🧠 Systematic traders who want quantified liquidity analysis — the hybrid pool detection, weighted scoring, and sweep state machine replace entirely subjective liquidity level identification with objective, repeatable criteria
📈 Traders who struggle with stop placement on liquidity entries — the sweep-anchored stop placement and opposing magnet TP provide the most structurally appropriate risk parameters available for liquidity-based trading
⚠ Traders who have been stopped out by cascading waterfall bars — the cascade block on same-bar entries and the delayed reclaim system together prevent the most common failure mode of liquidity trading: entering during a genuine continuation move rather than a reversal
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📝 Notes
All signals are confirmed on bar close — the indicator is non-repainting by design. Pool states, sweep state machine, setup conditions, and confluence scoring all finalize on confirmed bars only
The pivot cluster averaging system means that as new pivots near the same level form, the pool level gradually adjusts toward the weighted average. This means the active pool level may shift slightly over time as new evidence accumulates — this is intentional and produces more accurate pool level estimates than using only the first or last pivot
The cascade block applies only to the same-bar sweep entry (Setup A). Delayed reclaim entries (Setup B) are never blocked by cascade conditions — this is by design, as the cascade's resolution in subsequent bars is precisely the entry condition for Setup B
The delayed reclaim window starts from 1 bar after the sweep (barsSinceSslSweep >= 1). Same-bar reclaims are handled exclusively by Setup A. There is no overlap between the two setup types
When useMagnetTp is on and no opposing magnet is currently active (the opposing pool has not qualified or has been swept/invalidated), the system falls back automatically to the R-multiple TP without any gap in functionality
The Choppiness Index is the only hard filter in MAGNET. All other filters (HTF, volume, structural bias) are soft confluence layers that add or do not add to the score. This reflects the intentional philosophy that quality through combination is superior to quality through suppression
Maximum 500 labels and 500 lines are rendered. Pool lines are redrawn on the last bar, so they do not accumulate over history
The indicator does not track open positions or P&L and does not connect to any broker or account
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ Disclaimer
This indicator is a technical analysis and visualization tool intended for educational and informational purposes only. It does not constitute financial advice or a recommendation to buy or sell any financial instrument. All signals are generated from historical and real-time price data using mathematical calculations — their accuracy or profitability is not guaranteed. Past performance of any signal type does not guarantee future results. Always conduct your own analysis, use proper risk management, and consult a licensed financial advisor before making any trading decisions. The author accepts no responsibility for any losses incurred from the use of this indicator.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Built for traders who understand that price does not move randomly — it moves with purpose, toward the liquidity that institutions need, and away from it once that liquidity has been consumed. Wskaźnik
Wskaźnik
S/R Zone Flip Tracker v9.5 - SAMMYS/R Zone Flip Tracker
WHAT IT DOES
This indicator detects support and resistance zones from confirmed price pivots, then tracks when price breaks through a zone and "flips" its role - broken resistance becomes support, broken support becomes resistance. Flipped zones are recolored and highlighted for a configurable number of bars, and flip events fire markers and alerts. A ladder table lists the nearest zones above and below current price, sorted by distance, so you can read the immediate S/R structure at a glance without scanning the chart.
HOW IT WORKS
1. Zone creation: Swing highs and lows are detected with ta.pivothigh / ta.pivotlow. Each confirmed pivot creates a zone centered on the pivot price. Zone half-width is either a multiple of ATR (adaptive to volatility) or a fixed dollar amount, selectable in settings.
2. Zone maintenance: Nearby zones are merged when their midpoints fall within an ATR-based merge threshold. New pivots that land inside an existing zone's dedup radius are discarded instead of stacking duplicates. Zones farther from price than a distance cap (the larger of an ATR window and a percent-of-price window) are pruned, and if more zones remain than the per-mode maximum, the farthest ones are evicted. This keeps only the structurally relevant levels on the chart.
3. Flip detection: On each confirmed bar close, every zone is tested against the break method you select. "Close" requires the candle to close beyond the zone edge plus an ATR-based confirmation buffer. "Wick" allows the high/low to trigger the break. When a zone is broken upward it is reclassified as support; broken downward it becomes resistance. The flip bar is recorded so recently flipped zones render in a stronger highlight color and are tagged "S Flipped" / "R Flipped" until the highlight age expires.
4. Flip throttling: A minimum-bars-between-flips setting suppresses repeated flip signals on the same side within a short window, reducing noise in choppy conditions.
5. Trading modes: Scalping, Intraday, Swing, and Position modes each carry their own independent parameter set (pivot length, zone width, confirmation buffer, flip throttle, zone count, distance caps). "Auto" selects the mode from the chart timeframe. "Manual" exposes a fully custom set. This lets one script behave sensibly from 1-minute charts to weekly charts without retuning on every timeframe change.
6. EMA cloud: An optional 9/21 EMA cloud (lengths configurable) provides directional context behind the zones. Green fill when fast is above slow, red when below.
NON-REPAINTING DESIGN
All flip state changes are gated on barstate.isconfirmed, so flips, markers, and alerts only occur on closed bars and do not change after the fact. The optional higher-timeframe confirmation uses request.security with a confirmed-bar offset so the higher-timeframe value never previews an unclosed HTF bar: on closed chart bars it reads the current HTF value, and on the developing bar it reads the last closed HTF value. Pivots by nature confirm only after the right-side lookback completes, so zones appear a fixed number of bars after the actual swing point - this is inherent to pivot detection, not repainting.
HOW TO USE IT
- Leave Trading Mode on Auto to let the script pick parameters from your chart timeframe, or select a mode explicitly to tune it.
- Watch the ladder table for the three nearest resistance zones above price and three nearest support zones below, with price and percent distance for each. An asterisk marks recently flipped zones.
- "Flip Up" markers print when resistance is confirmed broken and reclassified as support; "Flip Dn" marks the opposite. These are commonly read as breakout-and-retest context: a fresh flip zone is a candidate area for price to retest from the other side.
- Enable MTF Close Confirmation to require the break to hold on a higher timeframe before a flip registers, which filters out breaks that only exist on the chart timeframe.
- Three alerts are available: flip to support, flip to resistance, and any flip.
SETTINGS SUMMARY
- Per-mode: pivot left/right length, zone width ATR multiple, confirmation buffer, minimum bars between flips, max zones shown, distance caps (ATR multiple and percent).
- General: ATR length, break method (Close or Wick), dedup and merge thresholds, zone width mode (ATR or Fixed $), flip highlight age.
- Visual: zone colors for support, resistance, and recently flipped states; EMA cloud toggle and lengths; ladder table position and font size.
LIMITATIONS
- Zones confirm pivot-right bars after the swing point (inherent lag of pivot detection).
- Flip markers older than the Flip Label Lookback are not redrawn on chart reload; live alerts are unaffected.
- Requires roughly pivot length plus ATR length bars of history before the first zones appear.
- This is an analysis tool, not a trading system. It does not predict price and generates no buy/sell recommendations. Wskaźnik
Chart Setup [Ribbon + WT Crossover + Flow]TITLE
Ribbon + WaveTrend Crossover + Money Flow
SHORT TAGLINE (for the summary field)
Trend ribbon, WaveTrend/RSI crossover engine, and money-flow confirmation unified in a single indicator — with a three-layer confluence signal, multi-symbol screener table, and full alert suite.
─────────────────────────────────────────────
FULL DESCRIPTION (paste into the publication page)
─────────────────────────────────────────────
█ OVERVIEW
This indicator merges three complementary layers of market analysis into one script, so a complete trend-following workflow loads with a single "Add to chart":
• PRICE LAYER — a two-EMA ribbon cloud that defines trend regime, a slow dotted baseline for macro bias, and "Long / Short Initiated" labels printed at ribbon flips.
• MOMENTUM LAYER — a selectable oscillator engine in its own pane: WaveTrend (default) or RSI + Signal. Blue vs red crossover lines with a shaded green/red regime background.
• VOLUME-FLOW LAYER — a Money Flow wave, normalized and drawn as a compact strip along the bottom of the pane, with "V" flags when flow confirms a fresh bullish impulse.
The script uses Pine's force_overlay capability so the ribbon, labels, and candle coloring render on the price chart while the oscillator and flow strip live in the indicator's own pane — one script, two visual domains.
█ WHY THESE THREE TOGETHER (mashup rationale)
Each layer answers a different question, and each has a known weakness that the others cover:
• The EMA ribbon defines direction but lags and whipsaws in chop.
• The oscillator crossover times entries earlier but fires false signals against the trend.
• Money flow validates whether volume actually supports the move.
The value of the mashup is the CONFLUENCE signal: a diamond prints (and an alert fires) only when all three agree simultaneously — ribbon flips bullish, oscillator line 1 is above line 2, and money flow is positive (mirrored logic for shorts). Individually these are common tools; combined gating is the point of this script.
█ HOW IT WORKS
Ribbon Cloud
Fast EMA (default 20) vs Slow EMA (default 50). The area between them is filled teal when fast > slow, pink when fast < slow. A slow SMA baseline (default 200) is drawn as a dotted line for higher-order bias. Labels print on crossovers of the two EMAs.
Oscillator Engine (selectable)
• WaveTrend mode (default): esa = EMA(hlc3, n1); ci = (hlc3 − esa) / (0.015 × EMA(|hlc3 − esa|, n1)); WT1 = EMA(ci, n2); WT2 = SMA(WT1, 4). Zero midline, configurable overbought/oversold levels (default ±60). WaveTrend concept credit: LazyBear.
• RSI + Signal mode: RSI (default 14) vs its EMA signal line (default 9), with 30/50/70 levels.
The pane background shades green while line 1 > line 2 and red otherwise, making regime changes readable at a glance.
Money Flow Strip
SMA(((close − open) / (high − low)) × multiplier, period), z-score normalized, clamped, and rescaled into a fixed band at the bottom of the pane (the band position auto-adapts to the active engine's scale). A "V" flag prints a configurable number of bars after flow crosses above zero while it remains positive.
Screener Table (optional, off by default)
A compact table on the price chart tracks up to five user-selected symbols on the chart timeframe, showing each symbol's ribbon regime (BULLISH / BEARISH) and the time of its most recent flip. Uses request.security without lookahead.
█ SIGNALS & ALERTS
• Ribbon Long / Ribbon Short — EMA ribbon flip
• Osc Bull Cross / Osc Bear Cross — oscillator line crossover
• Money Flow Bull — flow crosses above zero
• CONFLUENCE LONG / CONFLUENCE SHORT — all three layers aligned (diamond markers on chart)
All are standard alertcondition() alerts and work with webhooks.
█ INPUTS
Every parameter is exposed: ribbon lengths and source, engine selection, WaveTrend channel/average/signal lengths and OB/OS levels, RSI/signal lengths, background transparency, money-flow period/multiplier/flag delay, screener symbols and toggle, and every color used by the script.
█ HOW TO USE
1. Keep the default WaveTrend engine on intraday timeframes (15m shown in the chart example); switch to RSI + Signal if you prefer a bounded 0–100 oscillator.
2. Treat the ribbon as the regime filter: only take oscillator signals in the direction of the cloud color.
3. Use the confluence diamonds as the highest-conviction trigger, and the money-flow "V" flag as an add-on/continuation confirmation.
4. Tune the fast/slow EMA pair to your instrument's rhythm (13/48, 20/50, and 21/55 are common intraday pairs).
█ NOTES & LIMITATIONS
• Signals are evaluated on bar close; the regime background and cloud color on the live bar can change until the bar closes.
• The screener table reads the chart's timeframe for all symbols and is limited to five symbols to stay within request.security limits.
• hline() accepts constants only, so the engine-dependent mid/OB/OS levels are drawn as dotted plot() lines.
• This is a trend-following toolkit: expect whipsaws in low-volatility congestion; the confluence gate reduces but does not eliminate them.
█ CREDITS
WaveTrend oscillator concept: LazyBear (WaveTrend Oscillator ).
Money-flow wave construction is inspired by the money-flow component popularized in Market Cipher-style tools.
Ribbon cloud, engine unification, normalization/band placement, confluence gating, screener table, and all code in this script are original work.
█ DISCLAIMER
This script is for educational purposes only and is not financial advice. Trading futures and options involves substantial risk of loss. Always do your own research and test any tool on historical data and paper trades before using it with real capital.
─────────────────────────────────────────────
SUGGESTED TAGS
trend, wavetrend, rsi, moneyflow, ema, ribbon, crossover, confluence, screener, intraday
CHART TO PUBLISH WITH
Use a clean 15m chart of a liquid NSE F&O stock showing one clear ribbon flip with a confluence diamond, oscillator crossover, and money-flow flag visible — TradingView requires the published chart to clearly demonstrate the script's output with no unrelated drawings or other indicators. Wskaźnik
SPY/SPX Expected Move + Session Levels📊 Expected Move + Session Levels (SPY / SPX)
Plots the day's expected move band plus the key session levels — automatic, refreshed daily before the open, nothing to enter or maintain.
🔹 Draws: Expected Move High/Low (the one-standard-deviation daily range implied by options pricing, anchored at the prior close), Prior Day High/Low, and Overnight High/Low (from the ES futures overnight session, rescaled to your chart). Optional shaded band and info table.
⚙️ Settings: every level toggles on/off individually; colors, line width, and label size are adjustable. The overnight source, session window, and IV index can be changed, and setting Horizon to 5 with VIX approximates the weekly move. Best on intraday timeframes.
⚠️ Note: the expected move is a statistical estimate, not a boundary — price is expected to close inside the band roughly two days out of three, and beyond it roughly one in three. Treat the edges as context, not walls; the market will go where it chooses. All levels are built from CBOE volatility indices, daily session data, and CME ES futures. Informational only, not trading advice. Wskaźnik
Wskaźnik
Liquidity Sweep Levels ProLIQUIDITY SWEEP LEVELS PRO
WHAT IT DOES
Liquidity Sweep Levels Pro automatically detects buyside liquidity (BSL) and sellside liquidity (SSL) levels from confirmed swing pivots, draws them as horizontal lines that extend in real time, and identifies liquidity sweep events - moments where price wicks through a level to run resting stop orders and then closes back inside. It then applies a displacement-based confirmation model with confluence grading (A+/B/C) so you can distinguish genuine sweep reversals from continuation breaks.
The concept: swing highs accumulate buy stops and breakout orders above them (buyside liquidity); swing lows accumulate sell stops below them (sellside liquidity). When price pierces a level but fails to close beyond it, that liquidity has been consumed - a condition that frequently precedes a reversal toward the opposite pool. When price closes cleanly through a level instead, that is a break, and the indicator treats it as continuation rather than reversal.
HOW IT WORKS
Level detection: Swing highs and lows are identified using confirmed pivots (pivot length adapts to your chart timeframe in Auto mode, or can be set via Scalping / Intraday / Swing / Position / Manual modes). A pivot only becomes a level once fully confirmed - levels never appear retroactively.
Equal high/low clustering: New pivots forming within an ATR-based tolerance of an existing active level merge into it instead of stacking duplicate lines. Merged and retested levels grow thicker (up to 4x width), visually flagging multi-touch liquidity pools where the largest stop clusters accumulate.
Sweep vs break classification (mutually exclusive by construction):
SWEEP: wick pierces the level by at least the minimum pierce distance (ATR-based, configurable) but the bar closes back inside. Line turns dashed, sweep label prints.
BREAK: bar closes through the level. Continuation event, separate alert.
Displacement confirmation: A sweep alone does not confirm a reversal. After an SSL sweep, a later bar must close above the sweep bar's high within the confirmation window (default 5 bars) to print CONF LONG. Mirror logic for BSL sweeps and CONF SHORT. A close back through the sweep wick invalidates the setup; expiry cancels it silently.
Confluence grading: Each confirmed signal is graded using two optional filters measured on the sweep bar - EMA stack alignment (9/21/55) and relative volume (RVOL) - producing A+ (all confluences), B (partial), or C (none). A minimum-confluence gate can hard-filter signals if desired.
HOW TO USE IT
SSL SWEEP followed by CONF LONG: long setup. Stop below the sweep wick; first target is the nearest active BSL line above.
BSL SWEEP followed by CONF SHORT: short setup. Stop above the sweep wick; first target is the nearest active SSL line below.
Thicker lines mark multi-touch pools - sweeps of these levels are typically the higher-probability reversals.
The status table shows active level counts, nearest BSL/SSL prices, pending setup state with grade, and the last signal.
Six alerts are available: BSL/SSL Sweep, BSL/SSL Break, Confirmed Long, Confirmed Short.
Pine Screener support: persistent latched columns (sweep state, confirmed state, pending direction, confluence score, nearest levels, ATR distances) let you scan an entire watchlist for fresh sweep and confirmation events.
Suggested timeframes: 15m as the primary intraday chart; 5m for scalping in Scalping mode; 1H-Daily for swing context. On lower timeframes, raising Min Sweep Pierce (ATR) to 0.10-0.25 filters shallow wick grazes.
NON-REPAINTING DESIGN
All levels are created only from fully confirmed pivots, and all signals - sweeps, breaks, and confirmations - are evaluated strictly on confirmed bars. No signal, label, or line state changes retroactively. The inherent tradeoff of pivot-based detection is that a level appears only after its pivot confirms (pivot length bars after the actual swing); this is disclosed by design rather than hidden with lookahead.
SETTINGS OVERVIEW
Trading Mode: Auto (timeframe-adaptive) or fixed profiles / manual pivot length
Max Levels Per Side, ATR merge tolerance, retest tolerance
Min Sweep Pierce (ATR), swept/broken line handling
Confirmation Window, Min Confluence gate
EMA lengths, RVOL length and threshold, optional EMA plots
Full visual customization: labels, tags, colors, table position
LIMITATIONS AND NOTES
Levels require pivot confirmation, so the first bars of a session rely on levels carried from prior price action - prior-session highs and lows are typically the highest-quality pools.
Confirmation adds deliberate latency: the entry reference is the confirmation close, not the sweep close. This trades a later entry for a much lower false-positive rate.
This indicator identifies liquidity structure and event conditions. It is an analysis tool, not a trading system, and does not guarantee outcomes. Always apply your own risk management. Wskaźnik
MR8 Trend Direction & Signal IndicatorThe MR8 is a dynamic trend-following indicator built on the McGinley Dynamic moving average — one of the most responsive and self-adjusting smoothing algorithms available. Unlike traditional EMAs that can lag or whipsaw in changing market conditions, the McGinley Dynamic automatically adapts its speed based on market velocity, resulting in cleaner, more reliable signals.
How It Works
MR8 plots two McGinley Dynamic lines — a faster Ribbon 8 and a slower Ribbon 9. When the faster line crosses above the slower line, the ribbon turns white, signaling bullish momentum and a potential long entry. When the faster line crosses below, the ribbon turns grey, signaling bearish momentum and a potential short entry. This crossover method filters out the noise and false flips that plague single-line slope-based indicators.
Built-In Stop Loss
MR8 includes an optional visual stop loss line calculated directly from the ribbon's current value — 2% above the line for shorts, 2% below for longs. Toggle it on in settings to see exactly where your risk level sits relative to the indicator itself, on any timeframe.
Alert Ready
MR8 includes two built-in alert conditions — one for long signals and one for short signals — with a webhook-compatible JSON message format. Connect directly to any automated trading bot or notification system with zero additional configuration.
Best Used On
BTC/USD and BTC/USDT
55 minute, 1 hour, and higher timeframes
Futures and spot markets
Settings
Ribbon 8 Length — controls the speed of the faster line (default 12)
Ribbon 9 Length — controls the speed of the slower line (default 21)
Stop Loss % — distance from the ribbon for the optional SL line (default 2%)
Show Stop Loss Line — toggle the SL visualization on or off Wskaźnik
Wskaźnik
EMA Pro+ Suite# EMA Pro+ Suite
**A multi-layer EMA confluence framework for reading market state at a glance.**
---
## What It Is
EMA Pro+ Suite is an overlay indicator built around three exponential moving averages — a Fast (10), Mid (20), and Slow (50) EMA — organized into a structured three-layer state engine that tells you the current market regime, momentum direction, and whether price is in or out of alignment with that regime. Rather than treating each EMA in isolation, the suite reads them together as a system and surfaces a single, coherent market state at all times.
A corner dashboard table updates in real time, giving you an instant read on bias, momentum, alignment, EMA slopes, and price extension — without having to scan the chart manually.
---
## How It Works
The indicator evaluates three distinct layers on every bar:
**Layer 1 — Bias (Trend Regime)**
Defined by price relative to the 50 EMA. Price above = bullish bias. Price below = bearish bias. This is the macro filter — it determines which direction setups should be taken in.
**Layer 2 — Momentum**
Defined by the 10 EMA relative to the 20 EMA. When the fast EMA is above the mid EMA, momentum is bullish. When below, momentum is bearish. Momentum alignment with bias is the confirmation layer.
**Layer 3 — Price vs Fast EMA**
When bias and momentum are aligned but price is on the wrong side of the 10 EMA, the indicator flags a potential pullback or exhaustion condition. In a full bull regime, price dipping below the 10 EMA may represent a high-quality entry opportunity — or an early warning of trend exhaustion. Context determines which.
**Slope Engine**
Each EMA is evaluated for slope using a configurable lookback. RISING / FLAT / FALLING is displayed per EMA in the dashboard. A momentum flip on flat EMAs carries significantly less weight than one on rising or falling EMAs — this is critical for filtering out noise in ranging conditions.
**Price Distance from 50 EMA**
Tracks how extended price is from the slow EMA as a percentage. Large positive or negative readings flag mean reversion risk.
**Bar & Background Coloring**
- Green background + green bars = full bull alignment
- Red background + red bars = full bear alignment
- Yellow bars = conflicting bias and momentum (mixed / transitional state)
- Aqua bars = bull regime, price pulling back below 10 EMA
- Fuchsia bars = bear regime, price popping above 10 EMA
**Cross Signals**
- `M↑` (green) — 10 EMA crossed above 20 EMA in bull zone. Aligned, higher conviction.
- `M↓` (red) — 10 EMA crossed below 20 EMA in bear zone. Aligned, higher conviction.
- `M↑ 🐻` (orange) — Bullish momentum flip firing in bear zone. Counter-trend, lower conviction.
- `M↓ 🐂` (orange) — Bearish momentum flip firing in bull zone. Counter-trend, lower conviction.
**Multi-Timeframe Support**
All three EMAs can be calculated on a higher timeframe and plotted on the current chart. Use this to anchor your bias to the HTF structure while reading entries on a lower timeframe.
---
## Possible Ways to Use It
**Trend Following**
Wait for full alignment — green background, green bars, all three slopes RISING. Only look for long entries. Use the 10 EMA pullback (aqua bars) as a potential entry trigger. Reverse logic for shorts.
**Momentum Flip Entries**
Use aligned `M↑` / `M↓` signals (green/red) as entry triggers when bias and slope confirm. Discard or fade counter-trend orange signals unless you have a specific reason to trade against the regime.
**Regime Filter for Other Systems**
Use the bias layer (price vs 50 EMA) as a filter for another strategy. Only take long signals from your primary system when EMA Pro+ shows bull bias, and vice versa.
**HTF Confluence**
Set the EMA Timeframe to a higher timeframe (e.g. 4H or Daily) while trading on a 15m or 1H chart. The dashboard will show the HTF regime, giving you a structural anchor for your intraday reads.
**Avoiding Chop**
When all three slopes read FLAT and bars are yellow (mixed alignment), the market is in a transitional or ranging state. Consider standing aside or reducing position size until a clear regime re-establishes.
**Mean Reversion Awareness**
When Dist 50 shows a large positive or negative reading, price is extended from the slow EMA. In trending markets this can persist — but it raises the bar for adding to positions and flags potential snapback risk.
---
## Settings
| Setting | Description |
|---|---|
| EMA Timeframe | Blank = current chart timeframe. Enter any TF (e.g. 60, 240, D) for MTF mode. |
| Fast / Mid / Slow EMA Length | Default 10 / 20 / 50. Fully adjustable. |
| Slope Lookback | Number of bars used to calculate EMA slope. Increase on lower timeframes to reduce flat readings. |
| Show EMA Lines | Toggle the three EMA plots. |
| Show Bias Background | Toggle the green/red background tint. |
| Color Bars by State | Toggle bar coloring. |
| Show Cross Signals | Toggle M↑ / M↓ labels on chart. |
| Show Dashboard Table | Toggle the corner HUD. |
| Table Position | Top Right / Top Left / Bottom Right / Bottom Left. |
| Bar Close Reminder Alert | Fires a reminder alert on every bar close to check the setup. |
---
## Alerts
- Momentum Flip Bullish — Bull Zone (aligned)
- Momentum Flip Bullish — Bear Zone (counter-trend)
- Momentum Flip Bearish — Bear Zone (aligned)
- Momentum Flip Bearish — Bull Zone (counter-trend)
- Price Reclaimed 50 EMA (bias flipped bullish)
- Price Lost 50 EMA (bias flipped bearish)
- Bull Pullback Signal (bull regime, price below 10 EMA)
- Bear Pullback Signal (bear regime, price above 10 EMA)
- Bar Close Reminder
---
## Disclaimer
This indicator is provided for educational and informational purposes only. It does not constitute financial advice, investment advice, or a recommendation to buy or sell any asset. All trading involves substantial risk of loss. Past performance of any signal, strategy, or system is not indicative of future results.
EMA Pro+ Suite is a tool to assist with technical analysis — it does not predict price, guarantee accuracy, or remove the inherent uncertainty of financial markets. No indicator eliminates risk. You are solely responsible for your own trading decisions.
Always conduct your own research, apply proper risk management, and consider consulting a licensed financial professional before making any trading decisions. Only trade with capital you can afford to lose. Wskaźnik
SmartTraders Research Labs -Geometric Trend Lines - GTLGEOMETRIC TREND LINES (GTL)
GTL is a research indicator that studies the geometry of price structures. It freezes structural anchors in the past, stretches two right-triangles between those anchors and the live candle, and reads their angles inside a dimensionless coordinate space — then learns from every completed structure to estimate, with calibrated statistics, which way the current one is leaning. It is a structural analysis and research tool, not a trading system.
█ STEP OUT OF THE CHART PLANE
Every trader has drawn a trendline and called it steep. Steep compared to what? Stretch the chart window and the angle flattens. Jump from Bitcoin to a quiet blue-chip stock and a "45-degree rally" becomes a completely different animal. The chart plane mixes two quantities that were never meant to share axes — price and time — so any angle drawn on it is a property of your zoom level, not of the market.
My standard, before any geometry begins, is to take the shape out of the chart plane entirely. GTL maps every point into an Isotropic Coordinate System (ICS) where both axes are pure numbers:
y = log(price) / σ
x = bars / lookback
Price is expressed in units of the instrument's own volatility (σ, estimated with the Yang-Zhang method over 500 bars), and time in units of the analysis window. Nothing on either axis carries dollars, lira, satoshis or minutes anymore.
In this space, a degree finally means something. The angle
θ = atan(Δy / Δx) × 180 / π
is intrinsic: a 60° ceiling angle on gold's 30-minute chart describes the same geometric event as a 60° ceiling angle on a 3-minute meme-coin chart. The instrument's personality — its price level, its tick size, its temperament — has been normalized away, and what remains is pure trajectory. Everything else in this indicator stands on that ground.
The same rally, two zoom levels, two different angles — and on the right, the dimensionless ICS home where θ finally becomes a property of the market, not of your screen.
█ THE TRIANGLE — A SHAPE THAT CARRIES DATA
Of all the shapes humanity has leaned on, the triangle is the one that never let us down. It raised the pyramids, it holds every bridge truss and roof frame you have ever walked under, and it is the only polygon that cannot be deformed without changing the length of a side. Engineers call that property rigidity. I read it as trustworthiness — a triangle does not lie about its geometry.
That is why I chose it as the measuring instrument. On every structure, GTL constructs two right-triangles inside ICS:
The ceiling triangle — from the frozen HH anchor to the live candle's high.
The floor triangle — from the frozen LL anchor to the live candle's low.
Each triangle is not a drawing; it is a container. Four measurements live inside it at every bar:
θ — the signed angle of the hypotenuse, the indicator's core reading
Δy — the signed magnitude of the move in volatility units
area — the geometric surface the structure has swept
centroid — the shape's center of mass in ICS
While price grinds below a frozen ceiling, the ceiling angle sinks degree by degree into negative territory. When price presses up from a frozen floor, the floor angle climbs. Two triangles breathe with the market — one watching from above, one from below — and their angles are the raw language everything downstream of this indicator speaks.
One triangle watches from above, one from below — and θ, Δy, area and centroid live inside each of them.
█ AN ANCHOR IN THE PAST — MEASURING FROM CALM WATER
Picture a storm at sea, and two people trying to measure the waves. One stands on the shore. One sits in a boat, right among them. The observer on the shore, feet on solid ground, reads the height of every wave with precision — however wild the water gets, the ground beneath him does not move. The observer in the boat rises and falls with the very thing he is trying to measure; every number he writes down is contaminated by his own motion.
Most swing-based tools are the observer in the boat. Their reference points — the latest swing high, the latest swing low — are redefined by the market again and again, so any angle or distance measured from them mixes two movements at once: the price's, and the reference's own.
GTL plants its observer on the shore. At the birth of every structure, the highest high and the lowest low of the lookback window are frozen — locked to a fixed bar in the past — and from that moment they do not move. Every angle is measured from calm, settled water toward the storm of the live candle. The reading stays pure: when θ changes, it is because price moved, and for no other reason.
The anchors hold until price closes beyond one of them. That close is the break — the moment the structure completes, is archived with its full geometry, and a fresh pair of anchors freezes for the next chapter.
One naming note, so the chart reads correctly: what GTL labels HH and LL are these frozen anchor levels, not the traditional trailing swing highs and lows.
Solid ground measures the storm precisely; a boat measures mostly itself — GTL is the observer on the shore, and the frozen box below is exactly that shore.
█ WHY 23 — A PRIME WINDOW
The lookback window — the number of bars GTL scans before freezing a new pair of anchors — defaults to 23. The choice is arithmetic, not aesthetic.
23 is prime: its only divisors are 1 and itself. Stated as a condition,
gcd(23, k) = 1 for every k < 23
For a rolling window, that matters mechanically. If a periodic component of length k shorter than the window is present in the data, the window boundary does not keep meeting that component at the same phase. Because 23 and k are coprime, the alignment steps through all k possible phase offsets before it repeats. A composite window gives that protection away: 24 divides cleanly by 2, 3, 4, 6, 8 and 12, so components at those lengths can meet repeated window boundaries at the same phase, allowing anchor placement to inherit regularity from the measuring frame itself.
Engineering solved the same problem with hunting-tooth gear design: tooth counts are chosen coprime so each tooth eventually meshes with every counterpart, instead of the same pairs meeting forever and wearing a repeated pattern into the metal. Periodical cicadas offer a biological analogy — 13- and 17-year emergence cycles, both prime, reduce overlap with shorter recurring cycles.
This is a design principle stated in number theory, not a performance claim. A prime window does not make GTL better by itself, and it does not prove anything about future price. It simply reduces one avoidable source of arithmetic resonance, so repetition in the readings is less likely to be created by the measuring window. The lookback remains a user input; 23 is the default I stand behind.
Every window from 20 to 25 shares a divisor with at least one shorter cycle length — 23 is the only empty row, which is exactly why it is the default.
█ HOW THIS SERIES IS BUILT — CSV OUT, ANALYSIS IN
This episode follows a working method I now treat as the standard for the whole series: nothing ships on intuition alone. The indicator exports its own internal life — every angle, every structure, every break — as plain columns in the Data Window, ready for CSV export. Before publication, those exports were analyzed with AI assistance across a deliberately diverse panel:
7 instruments × 2 timeframes = 14 datasets
gold, Bitcoin, Tesla, Brent crude, Turkish Airlines, Dogecoin, Saudi Aramco
30-minute and 3-minute bars — roughly 550,000 bars, ~30,000 completed structures
What came back from that study entered the code as design decisions, not as promises. Exactly five constants in the learning layer are hard-coded. They are not presented as universal truths or performance guarantees; they are documented design constants selected from the development study and kept fixed so the live model remains transparent and reproducible:
CAL_LAMBDA = 0.999 — fading-factor decay for the calibration counters
CAL_JUMPTH = 2.0 — empirical jumpiness threshold between steady and choppy estimates
CAL_MINW = 30 — minimum effective sample weight before a calibration cell is trusted
CAL_ROLL = 20 — length of the live recent-record window
JUMP_WIN = 5 — bars used for the short-term stability measurement
The methods behind the layer are standard enough to be named — fading-factor prequential counting for online calibration, adaptive Gaussian KDE for local probability estimation, and Kish-style effective sample size for weighted evidence — and the next section walks through each of them with its reference. The fixed values above are GTL's calibrated defaults from that study, not claims that these numbers are optimal for every market, symbol, or timeframe. Everything else the statistics need — bandwidth, confidence, significance — is computed live from the chart's own history.
Two honest disclosures. First, this analysis is development documentation, not an independent audit, and this description makes no accuracy claims from it. Second, the same door is open to you: every column used in that study is exported by the script itself, so you can pull the CSV from your own chart and put the same questions to any tool you trust.
The build loop of this series: the script exports its own life as CSV, analysis turns it into five documented design constants, and the same door stays open to every user.
█ FROM GEOMETRY TO STATISTICS — THE MATH, WITH ITS REFERENCES
An angle is a measurement; an estimate is a statement. Moving from one to the other honestly requires statistics. GTL does not present this layer as a private invention. It combines established statistical components, named here with their sources, and applies them to one specific object: the geometry of frozen price structures.
Volatility normalization. The σ in the ICS y-axis comes from the Yang-Zhang volatility estimator (Yang & Zhang, Journal of Business, 2000). It uses open, high, low and close data, including overnight, open-to-close and Rogers-Satchell-style range components. In GTL, this is what lets angles be measured in volatility-normalized space instead of raw price units.
Local probability. While a structure is alive, its current angle pair (θC, θF) is compared with archived breaks. Each historical break receives a Gaussian weight that decays with distance in angle space. This is a Gaussian KDE-style local weighting scheme. Its bandwidth follows Silverman's rule-of-thumb logic for two dimensions, h = σ̂ · n^(−1/6), recomputed from the chart's own history. Nothing is manually tuned.
Honest sample size. Weighted evidence can look larger than it really is: many tiny weights are not the same as many strong neighbors. GTL therefore uses the Kish effective sample size (Kish, Survey Sampling, 1965),
n_eff = (Σw)² / Σw²
to estimate how much effective evidence the weighted neighborhood actually contains.
Probability with humility. The weighted up/down vote is passed through a Beta(1,1) posterior, using n_eff as the effective evidence scale. The label only speaks when the posterior mean clears a one-sided 95% normal-approximation check against the 50/50 baseline. When that threshold is not met, the label does not force a call; it simply says the structure is too close to call.
Verification. The principle that probability forecasts must be scored against what actually happened goes back to Brier's 1950 paper in Monthly Weather Review, "Verification of Forecasts Expressed in Terms of Probability." In GTL, every estimate is graded when the break reveals the outcome.
Online calibration. Graded outcomes update fading-factor prequential counters, following the stream-learning evaluation framework of Gama, Sebastião and Rodrigues (Machine Learning, 2013). Fresh evidence receives more weight, while older evidence decays with λ = 0.999. The display can therefore show both the raw estimate and how estimates of the same kind have behaved on the current chart.
Stability. GTL also tracks estimate "jumpiness": the population standard deviation of the last five probability readings. The term and the general idea come from ensemble-forecast consistency research, especially Zsóter, Buizza and Richardson (Monthly Weather Review, 2009). GTL uses a chart-specific adaptation of that idea: a steady estimate and a choppy estimate are labeled differently, because a choppy estimate may still flip.
Nothing in this chain is exotic, and none of it is a performance guarantee. The original part is where the chain is pointed: at frozen structural geometry, measured inside a dimensionless coordinate space.
█ WHAT YOU SEE ON THE CHART
Frozen anchors. Two dashed horizontal lines mark the frozen HH and LL of the current structure, each with its exact level, and a dotted vertical line marks the anchor bar in the past where the freeze happened. These lines do not trail price — that is the whole point.
Geometric trend lines. Two solid lines run from the anchors to the live candle: ceiling from HH to the current high, floor from LL to the current low. They are the triangle hypotenuses. When the two lines converge, they stop at their intersection instead of crossing. The live θC and θF values sit as labels at the anchor.
Structure boxes. Every completed structure is archived as a box: one border color for structures that broke up, another for structures that broke down, and a dashed box for the structure still being built. How many past boxes you see is your choice.
Angle map. A table sorts the recent breaks by their break angles — ceiling side and floor side, each with direction and duration. An arrow row shows where the current live reading ranks among them, so you can literally see where "now" sits in the break history. The footer row carries the up/down estimate; once the calibration cell has enough samples, it shows two numbers, raw → calibrated.
Estimate label. A label floats ahead of the last candle and speaks in sentences: which direction the odds favor, what signals of this kind have actually done on this chart (or the estimated odds while calibration is still warming up), whether the signal is steady or choppy, and a living record — how many of the last 20 estimates were right. It only takes a side when the significance check passes; otherwise it says, honestly, that the structure is too close to call.
The pending phase. Between a break and the next freeze, preview anchors appear as dotted gray lines, the table shows an hourglass, and the estimate quietly switches to a second model trained on pending-phase angles to estimate the direction of the NEXT structure's break.
One disclosure that matters: on the live bar, angles and estimates can change until the candle closes. Everything the indicator learns from — and every alert it fires — reads confirmed bars only.
█ UNDER THE CHART — 29 EXPORTED COLUMNS
Everything drawn above is only a rendering. The numbers underneath are all exported to the Data Window, which means TradingView's "Export chart data" hands you a complete CSV audit trail:
Live geometry & estimate, every bar:
Ceiling θ / Floor θ — the two live angles in ICS
Probability UP / Probability DOWN — the per-bar estimate (these two are also plots, so you can build threshold alerts on them directly)
Log Jump Bar — the stability (jumpiness) of the estimate
Log Cell Bar — which calibration cell this bar fell into
Structure snapshot, printed on every break bar:
Str Duration — how many bars the structure lived
Str Frozen HH / Str Frozen LL — the anchor levels
Str Max High / Str Min Low — the extremes reached inside
Str θ Ceil @Max / Str θ Floor @Min — the angles at those extremes
Str Break Dir — +1 up, −1 down
Estimate audit trail, on birth and break events:
Log Event — 1 = birth, 2 = break, 3 = both on one bar
Log θC Birth / Log θF Birth / Log P Birth / Log Sig Birth / Log nEff Birth — the forecast made the moment the structure was born
Log θC Pend / Log θF Pend / Log P Pend / Log Sig Pend / Log nEff Pend — the pending-phase forecast carried into this break
Log Hit Birth / Log Hit Pend — each forecast graded 1 or 0 against the actual break
Log Acc Birth / Log Acc Pend — the running accuracy of each estimate type
This is the same door the development study walked through. Export the CSV from your own chart, open it in a spreadsheet, in Python, or hand it to an AI assistant — and audit every sentence the label has ever told you.
█ SETTINGS THAT STAY OUT OF YOUR WAY
The settings menu is deliberately small: the lookback window, a few visual choices — colors, transparency, border style, table position, label size and offset, how many past boxes to show — and simple on/off toggles. That is the whole surface, because everything statistical is computed live from the chart itself: the KDE bandwidth from Silverman's rule, the effective sample size from Kish's formula, significance from the posterior, the calibrated rate from the fading counters, the pending-phase model switching in and out on its own. There is nothing to tune, and that is by design. The five documented constants from the development study are the only fixed numbers in the machine.
█ ALERTS
Three alerts cover the estimate's life cycle: Signal turns up, Signal turns down, and Signal gets choppy. Each fires once, on entering its state, and reads only confirmed bars — so what fired is what you will still see on the closed candle. For custom thresholds, Probability UP and Probability DOWN are exposed as plots: build Crossing Up or Greater Than alerts on them directly in TradingView's alert dialog, at any level you like, as many as you like. Recommended frequency: Once Per Bar Close.
█ SEVENTEEN LANGUAGES
The angle map, the anchor labels and the estimate label speak 17 languages: English, Türkçe, Deutsch, Italiano, Français, Español, Bahasa Indonesia, Bahasa Melayu, Ελληνικά, Русский, 中文, 日本語, 한국어, हिन्दी, العربية, فارسی and עברית. Right-to-left scripts — Arabic, Persian, Hebrew — mirror the table layout automatically. One honest limitation: input settings and alert messages stay in English, because Pine requires compile-time constant strings there.
█ WHAT THIS IS — AND WHAT IT IS NOT
GTL is a research and structural analysis tool. It measures the geometry of frozen price structures, keeps honest statistics about its own estimates, and shows you both — the raw number and the track record, side by side. It is not a trading system, its estimates are not trade signals, and nothing in this script or this description is financial advice. The calibrated rates describe what has already happened on your chart's own history; they are not a promise about the next bar. On the live candle, readings can change until the close — confirmed statistics and learning update on closed bars only.
Read it the way it was built to be read: as an instrument standing on the shore, measuring the storm. Wskaźnik
Wskaźnik
Strata - Regime Segments & Volume ProfileThis indicator segments price with a model-based online change detector, classifies every segment into a six-cell regime grid, and renders for each segment an exact regression line, a sigma channel, and a slanted volume profile. One standard runs everything: the segment is the state — there is no second bar-by-bar machine, no smoothing triggers, no dwell locks. The CUSUM cut threshold is the only persistence mechanism.
Detection. A Kalman local linear trend filter estimates a drifting level and a drifting slope, so a steady trend is what the model expects and trend drift is not mistaken for structural change. Each bar the filter emits the one-step innovation, standardized by its own recursively estimated variance. A two-sided CUSUM watches the standardized innovation mean; when it crosses the threshold the trend has structurally changed and a segment is cut, backdated to where the winning CUSUM run started, so the boundary lands where the change began rather than where it was detected. Cuts that would close a segment shorter than the minimum length are discarded and merged, so tiny fragments cannot exist. After an accepted cut the Kalman covariance is briefly inflated for faster re-adaptation. A second CUSUM on the innovation dispersion always runs and fires an alert on volatility shifts; a switch lets it cut segments too. The threshold h is derived from the data by default: you state the average segment length you want, and a feedback controller nudges h bar by bar until the realized average matches it — the panel shows the current h and the realized length so you can watch it converge. A fixed-h mode remains available; with the standard allowance k = 0.5, h = 4 corresponds to an average false-alarm interval of roughly 168 bars and h = 5 to roughly 465.
Classification. Direction is the segment's OLS slope per bar in units of the segment's mean daily sigma; below the dead zone in magnitude the segment is flat, so a violent sideways stretch is not forced into a bullish or bearish color. Tempo is the segment's mean volatility percentile against one threshold. The grid is direction times tempo: Up, Flat, Down crossed with Calm and Hot, six cells. Finalized segments get their one-shot call at the cut; the active segment is classified from its own tentative regression from birth, and the call may drift while the segment is young — that is accepted by design, since tentative regressions are tentative. A dashed vertical divider is drawn at every backdated cut and is the one authoritative boundary marker: between two dividers there is exactly one segment — one regression line, one profile, one state label. Labels and flat-state strokes adapt to the chart theme so they stay visible on light and dark backgrounds.
Volume profile. Volume is binned in residual space — by distance from the segment's regression line — and drawn as parallelogram bars running parallel to the channel, anchored to the segment's right edge and growing leftward, so a profile always butts against its own boundary. Bin width follows the Freedman–Diaconis rule with volume-weighted quantiles and the Kish effective sample size, with a fixed-bin fallback. The point of control and a seventy percent value area are drawn parallel to the fit. Profile bars use a direction-only palette, green up, red down, grey flat, with adjustable opacity. Segments too short to support a meaningful distribution simply skip the profile, and older segments are demoted to line plus POC to respect drawing limits.
Gauges. Pressure reads how close the active segment's readings sit to their classification boundaries, plus CUSUM cut progress when it opposes the current direction, normalized to a percentage with the implied target state. It is a gauge, not a calibrated probability — it catches gradual drifts only, and a cut can fire and reclassify from zero pressure. Hist. next reports the empirical next-state distribution from this chart's own transition history; the sample count is shown and should be read. Hidden data-window plots expose State, Direction, Tempo, and state age for use in the Pine Screener, and alerts cover segment cuts, volatility shifts, state changes, and every direction or tempo transition.
Scope. All decisions run on confirmed bars only: nothing repaints, finalized drawings are created once and never moved, and the active segment is the only mutable object. This is an online, causal detector — detection delay is irreducible for any causal method, and globally optimal offline methods such as PELT place breakpoints more accurately in hindsight. Treat segments, states, and gauges as context, not trade signals. The detection core is shared with the companion indicator "Strata Core"; keep the constants in sync if you run both. The presentation concept — per-segment regression channels and a trend-slanted volume profile — is inspired by "Dual Log Regression Channels" by BigBeluga and "Volume Cluster Profile (VCP)" by Zeiierman; the detection, classification, and estimation pipeline is an independent implementation of the methods below. Methods follow standard results in filtering, change-point detection, and density estimation (Kalman 1960; Harvey 1989; Page 1954; Moustakides 1986; Hinkley 1971; Lorden 1971; Mehra and Peschon 1971; Severo and Gama 2010; RiskMetrics 1996; Freedman and Diaconis 1981; Kish 1965; Maheu and McCurdy 2000; Ang and Timmermann 2012; Pagan and Sossounov 2003). Wskaźnik
Wskaźnik
Wskaźnik
HTF C2 Sweeps & Candles (v6 Streamlined)First and foremost, huge thanks and full credit to the original creator, wintonbanks, for the foundational logic and concept of this indicator. This script is a modified and optimized version of their excellent work. You can find the original, feature-rich indicator here:
This version has been published to offer a more streamlined, visually minimal experience while upgrading the backend to Pine Script v6.
Key Changes from the Original:
Pine Script v6: Upgraded the code to v6, including logic optimizations to prevent compiler warnings and improve performance.
Simplified Global Styling: Removed the individual timeframe line settings. Sweep lines are now controlled via a single "Global Styling" menu for a faster setup and cleaner settings panel.
Dynamic Sweep Labels: Added a custom labeling engine. Instead of drawing lines with side labels, this version dynamically calculates the center of active sweep lines and places clean, customizable labels (with background and text color options) directly on them.
Decluttered Chart: Completely removed the Previous High/Low lines, line extension toggles, and timeframe dots. This version focuses strictly on core sweeps and PO3 candles.
Custom Alert Sessions: Replaced the hardcoded London/New York session alert toggles with native Pine Script session inputs, allowing you to define your exact custom alert windows and timezones. Wskaźnik
Wskaźnik
VWAP+ [Y.Algo]VWAP+ — Five Anchored VWAPs, Rolling Multi-Exchange VWAP Bands, Previous-Period Zones & Session Initial Balance
VWAP+ layers up to nine independent VWAP structures on a single chart — five freely anchored VWAPs (Day through Year), four rolling-window VWAPs with optional cross-exchange aggregated volume, a snapshot of the previous completed period's VWAP channel, and a session Initial Balance box — so you can read fair value across every timeframe you trade at once, without switching charts or stacking multiple indicators.
Fully open-source (CC BY-NC-SA 4.0) — every calculation is documented below and visible in the script.
🔶 USAGE
VWAP+ is built as a multi-timeframe fair-value reference wall rather than a single-signal indicator. Instead of one VWAP, you can stack five independently anchored VWAPs (assign each to Day, Week, Month, Quarter, or Year) alongside four rolling VWAPs on any day-count window you like, and watch how price behaves against all of them at once. When several VWAPs converge into a tight band, that price zone tends to act as a stronger confluence support/resistance; when they fan apart, the market is caught between competing fair-value references on different horizons.
Anchored VWAPs are best for framing swing/position bias — set slots to Week, Month, Quarter and Year to see at a glance whether price sits above or below the "institutional" fair value on each horizon simultaneously, and treat a reclaim or loss of any of them as a potential regime shift on that timeframe. Rolling VWAPs behave differently: because they use a fixed trailing time window instead of resetting at a period boundary, they never gap at a session or period open, which makes them a smoother, more consistent reference on 24-hour markets like crypto.
The Previous VWAP Markers extend a fixed snapshot of the last (or second-to-last) completed period's VWAP channel to the right edge of the chart, giving you a static historical reference band to judge whether current price is trading rich or cheap relative to where the market closed out its last day, week, month, quarter, or year. Combine this with the Initial Balance box — built from the first hour of the Tokyo session — as a session-range reference, and use the touch alerts so you don't have to watch every VWAP manually.
🔹 Background Mode — Three-Way Color Management
VWAP+ carries no bull/bear theme, since it's a reference-line tool rather than a trend/signal indicator. Instead, a single three-way Background Mode switch governs the color of every VWAP, deviation band, previous-period marker, and Initial Balance box at once. Dark Background and Light Background each lock in a fixed palette tuned for that chart tone and override every individual color picker below, so most users can flip one switch and never worry about visibility again. Switching to Custom releases that lock — every color you've set on each VWAP, band, marker, and the IB box is used exactly as configured, putting visibility fully in your hands. In total, 36 individual color settings across five anchored VWAPs, four rolling VWAPs, eight previous-period markers, and the Initial Balance box are governed by this one switch.
🔹 Five Independent Anchored VWAPs
Five separate VWAP slots (VWAP1–VWAP5) can each be assigned its own anchor period — Day, Week, Month, Quarter, or Year — and toggled on independently, all off by default so you build exactly the combination you need. Each slot plots its own VWAP line plus a 1-standard-deviation upper/lower band with a fillable zone, all in fully customizable colors, letting you view several timeframes' fair value simultaneously on one chart.
🔹 Previous-Period VWAP Zone Markers
Eight independent toggles (previous day, week, two-back week, month, two-back month, quarter, two-back quarter, and year) each draw the corresponding completed period's VWAP channel — upper band, lower band, and VWAP line — as a box and labeled line projected to the right edge of the chart. This is a frozen historical snapshot, not a live-updating series, giving you a stable reference to compare current price against where the market's fair value settled in a prior period.
🔹 Rolling VWAP with Optional Multi-Exchange Aggregated Volume
Four independent rolling-window VWAPs (7D/30D/90D/365D by default, but each day-count is fully adjustable from a preset list) compute a true trailing-window VWAP that never resets at a period boundary. An optional aggregated-volume mode combines volume from up to four separately configured symbols (defaulting to BTC pairs across four major exchanges, but changeable to any instrument) before feeding the VWAP calculation — useful for markets where volume is fragmented across multiple venues. Deviation bands around each rolling VWAP can be switched between a percentage-based Symmetrical mode and a statistical Standard (standard-deviation) mode, with an adjustable multiplier controlling band width.
🔹 Initial Balance Range (Tokyo Session)
A box is drawn from the Tokyo trading session (09:00–15:00), with its high/low seeded by the first hour of that session (09:00–10:00) — the classic "Initial Balance" concept from auction market theory. The box extends across the full session and a configurable number of recent days remain visible on the chart, letting you gauge whether the current session is breaking out of, or staying contained within, its opening-hour range.
🔹 Touch Alert System
Nine independently toggleable alerts fire the instant price wicks touch any enabled anchored VWAP (VWAP1–VWAP5) or rolling VWAP (7D/30D/90D/365D), regardless of approach direction — a direction-agnostic heads-up that price has reached a fair-value reference worth reviewing, delivered once per bar close.
🔶 DETAILS
VWAP+ is fully open-source (CC BY-NC-SA 4.0). Here is exactly how it works.
Background palette — Dark and Light modes each route every color input through a single switch function into one of two hard-coded palettes: a high-transparency white-based set for Dark backgrounds, or a darker navy/grey set for Light backgrounds. While either fixed mode is active, the color pickers below are still evaluated but their values are discarded. Selecting Custom short-circuits that switch and returns each color input unchanged, so every picker takes effect.
Anchored VWAPs — Each of the five slots calls Pine Script's built-in ta.vwap(source, new-period-flag, 1) on hlc3, where the new-period flag fires on timeframe.change('D'/'W'/'M'/'3M'/'12M') depending on the chosen anchor. The VWAP and its bands reset to zero accumulation at the start of each anchor period; the multiplier of 1 draws bands at one volume-weighted standard deviation of price around the VWAP, widening or narrowing as the period progresses.
Previous-period markers — On every bar the script caches the just-completed period's upper band, lower band, and VWAP value (sampled one bar before the reset). Once the chart reaches its last bar, these cached values are drawn once as a static box, a dotted VWAP line, and three labels — they do not update afterward; they are a fixed snapshot, not a live series.
Rolling VWAP — Unlike the anchored VWAPs, this path uses the PineCoders ConditionalAverages library to sum price×volume, volume, and volume×price² over a fixed trailing time window (the day-count converted to milliseconds), computed fresh on every bar: VWAP = Σ(price·volume)/Σvolume, variance = Σ(volume·price²)/Σvolume − VWAP² (floored at zero), σ = √variance. In Standard mode, bands = VWAP ± multiplier×σ. In Symmetrical mode, bands = VWAP ± (multiplier/100)×VWAP — a flat percentage envelope rather than a statistical one.
Aggregated volume — When enabled, the script pulls volume via request.security from up to four independently configured symbols and sums them before it feeds the rolling VWAP formula above, in place of using only the current chart's own volume. This is designed for instruments whose real volume is fragmented across multiple venues (the default four fields point at the same crypto pair listed on four different exchanges), but the symbol fields can be changed to any ticker.
Initial Balance — Two Tokyo-time session windows are compared bar-by-bar: a 1-hour opening range (09:00–10:00) that seeds a box's high/low the moment it starts, and the surrounding full session (09:00–15:00) across which that box's right edge is extended. A rolling array retains only the most recent N day-boxes (the configured day count), deleting the oldest box once that limit is exceeded.
Alerts — Every alert fires at most once per bar close, formatted as: VWAP+｜{ticker} {timeframe} {price}｜{event name}.
🔶 SETTINGS
🔹 Background Mode
Background Mode : Dark Background (default) / Light Background / Custom. Dark and Light each lock every VWAP, band, previous-period marker, and IB color to a fixed palette tuned for that background tone — the color pickers below have no effect in these two modes. Custom releases the lock and uses exactly the color you've set on each line.
🔹 Anchored VWAP Settings (VWAP1–VWAP5, five independent slots)
VWAP1 / VWAP2 / VWAP3 / VWAP4 / VWAP5 : Enables that slot; all five are off by default.
Anchor Period : Day / Week / Month / Quarter / Year — sets when that slot's VWAP resets.
VWAP : Line color for that slot.
Bands : Color for the 1-standard-deviation upper/lower bands.
Fill : Color for the band-fill zone.
🔹 Previous VWAP Markers
pDay / pWeek / ppWeek / pMonth / ppMonth / pQuarter / ppQuarter / pYear : Each toggle draws that completed period's VWAP channel (box + line + labels) projected to the right of the chart; all off by default.
Color (per marker) : Sets the box/line/label tint for that specific marker.
🔹 Rolling VWAP
7D / 30D / 90D / 365D : Enables that rolling-window slot; all four are on by default.
Day Count : Choose the rolling window length from a preset list (1/3/5/7/14/21/28/30/60/90/182/365 days) — independent of the slot's label.
RVWAP : Line color for that slot's rolling VWAP.
Bands : Color for that slot's deviation bands.
Fill : Color for that slot's band-fill zone.
🔹 Rolling VWAP StdDev Bands
Use Aggregated Volume : Combines volume from the checked exchanges below into the rolling VWAP calculation instead of using only the current chart's volume.
Deviation Bands : Symmetrical (flat percentage bands around VWAP) or Standard (statistical standard-deviation bands).
Multiplier : Scales band width (minimum 0.5, in steps of 0.5).
Exchange 1 / 2 / 3 / 4 : Toggles whether that symbol's volume is included in the aggregate.
Symbol fields (Exchange 1–4) : Set which instrument's volume feeds each exchange slot — default to the same pair across four major exchanges, but any symbol can be used.
🔹 Initial Balance Range
Show IB Range : Toggles the Initial Balance box, built from the Tokyo session (09:00–15:00, with the 09:00–10:00 opening range defining the box's high/low).
Days : How many days of IB boxes stay visible before the oldest is removed.
Color : Box border/fill tint.
🔹 Alerts
VWAP1–VWAP5 Touch : Fires once per bar close the instant price wicks touch that anchored VWAP, regardless of direction (that VWAP must be enabled).
7D/30D/90D/365D RVWAP Touch : Same touch logic for each enabled rolling VWAP.
🔶 DISCLAIMER
This indicator and all its signals, markers, and alerts are provided for technical analysis study and research reference only. They do not constitute investment advice, financial advice, trading recommendations, or solicitations to buy or sell any asset. Financial market trading involves substantial risk; investors may lose part or all of their principal. Past performance does not represent and does not guarantee future results. All trading decisions made using this indicator are the sole responsibility of the user. The author and publishing platform assume no legal liability. Please fully understand market rules and your own risk tolerance, and consult a licensed professional financial advisor when necessary.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
中文版本 CHINESE VERSION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
VWAP+ | 多重VWAP通道 — 5組獨立錨定VWAP、滾動多交易所VWAP帶、前期區間標記與時段初始平衡
VWAP+ 在同一張圖表上疊加最多九組獨立的 VWAP 結構——五組可自由錨定的 VWAP（日至年）、四組可選聚合多交易所成交量的滾動 VWAP、前一完整週期 VWAP 通道的靜態快照，以及一個時段初始平衡箱型——讓你不必切圖或疊多個指標，就能同時讀懂各個你在交易的時框上的公允價值。
完全開源（CC BY-NC-SA 4.0）——以下完整說明每一項計算，原始碼公開可查。
🔶 用途說明
VWAP+ 的設計是一整面「多時框公允價值參考牆」，而非單一訊號指標。你可以疊上五組獨立錨定的 VWAP（各自指定日／週／月／季／年），再搭配四組可自訂天數窗口的滾動 VWAP，同時觀察價格對所有這些線的相對位置。當多條 VWAP 收斂成一條窄帶，該價格區往往形成較強的支撐壓力匯聚；當它們彼此散開，代表市場正被不同時框的公允價值參考拉扯。
錨定 VWAP 較適合用來框定波段／部位偏向——把插槽設定為週、月、季、年，即可一眼看出價格是否同時站在（或跌破）各個時框的「機構級」公允價值之上，並把任一條線的站回或跌破視為該時框上潛在的盤勢轉換。滾動 VWAP 的行為不同：因為它以固定的回看時間窗滾動、而非在週期邊界重置，所以不會在時段或週期開盤時跳空，在加密貨幣這類 24 小時市場上是更平滑、更一致的參考線。
前期 VWAP 標記會把上一個（或上上一個）已完整結束週期的 VWAP 通道，以固定快照的形式投影到圖表右側，讓你有一條靜態的歷史參考帶，用來判斷目前價格相對於市場上次收在哪個公允價值區間是偏貴還是偏便宜。搭配以東京時段第一小時建立的初始平衡箱型作為時段區間參考，再啟用觸及警報，就不必手動盯著每一條 VWAP。
🔹 背景模式——三段式配色管理
VWAP+ 沒有多空主題色（因為它是參考線工具，不是趨勢／訊號指標），改用「背景模式」三選一，一次管理所有 VWAP、標準差帶、前期標記與 IB 框的顏色。黑色背景與白色背景各自鎖定一組對應該背景色調的固定配色，並會覆蓋下方每一條線的個別顏色設定，讓大多數人一鍵切換就不必煩惱可見度。切到「自訂」則解除鎖定，完全依你在每條 VWAP、每組標準差帶、每個前期標記與 IB 框個別設定的顏色顯示，可見度自己把關。全指標共 36 個顏色設定點——5 條錨定 VWAP、4 條滾動 VWAP、8 個前期 VWAP 標記、1 個 IB 區間框——皆由這個開關統一控管。
🔹 5組獨立錨定 VWAP
五個獨立的 VWAP 插槽（VWAP1–VWAP5）各自可指定錨定週期——日、週、月、季、年——並各自獨立開關，預設全部關閉，讓你自由組合出所需的時框組合。每個插槽各自繪製其 VWAP 線，搭配 1 個標準差的上下帶與可填色區域，顏色皆可完全自訂，讓你在同一張圖上同時檢視多個時框的公允價值。
🔹 前期 VWAP 區間標記
八個獨立開關（前日、前週、前前週、前月、前前月、前季、前前季、前年）各自會把對應已結束週期的 VWAP 通道——上帶、下帶與 VWAP 線——以箱型加標籤線的形式投影到圖表右側。這是一個凍結的歷史快照，而非即時更新的序列，提供一條穩定的參考帶，用來比較目前價格相對於市場上一個週期收在哪個公允價值區間。
🔹 4組滾動 VWAP（可選聚合多交易所成交量）
四組獨立的滾動窗口 VWAP（預設 7D／30D／90D／365D，天數皆可從預設清單自由調整）計算真正的「回看時間窗」VWAP，不隨任何週期邊界重置。可選的聚合成交量模式會合併最多四個獨立設定標的的成交量（預設指向四大交易所的 BTC 交易對，但可改為任何標的）後再送入 VWAP 計算——適合成交量分散在多個交易場所的市場。每組滾動 VWAP 周圍的偏差帶，可在「百分比對稱」與「統計標準差」兩種模式間切換，並可用倍數調整帶寬。
🔹 初始平衡區間（東京時段）
以東京交易時段（09:00–15:00）畫出箱型，其高低點由該時段的第一小時（09:00–10:00）決定——這正是拍賣市場理論中經典的「初始平衡（Initial Balance）」概念。箱型會延伸涵蓋整個時段，且可設定保留在圖表上的天數，讓你判斷當前時段是正在突破、還是仍被限制在開盤第一小時的區間內。
🔹 觸及警報系統
九個獨立開關的警報，會在價格影線碰觸任一啟用中的錨定 VWAP（VWAP1–VWAP5）或滾動 VWAP（7D/30D/90D/365D）的瞬間觸發，不分逼近方向——單純提醒你價格已到達一條值得關注的公允價值參考線，於每根 K 棒收盤時最多觸發一次。
🔶 技術細節
VWAP+ 完全開源（CC BY-NC-SA 4.0），以下完整說明運作方式。
背景配色——黑色與白色模式皆透過同一個切換函數，把每個顏色設定對應到兩組寫死的固定配色之一：黑色背景使用高透明度的白階配色，白色背景使用較深的藏青／灰階配色。固定模式生效時，下方的顏色選擇器仍會被讀取，但其數值會被捨棄不用。選擇自訂則直接跳過此切換，原樣傳回你所設定的每個顏色，讓每個選色器都實際生效。
錨定 VWAP——五個插槽各自呼叫 Pine Script 內建函數 ta.vwap(source, 週期起始旗標, 1)，以 hlc3 為價格來源；週期起始旗標依所選錨定週期由 timeframe.change('D'/'W'/'M'/'3M'/'12M') 觸發。VWAP 與其帶線會在每個錨定週期開始時重置累積歸零；倍數 1 代表帶線畫在「以量價加權的價格標準差」1 倍處，隨週期推進而擴張或收窄。
前期標記——每根 K 棒都會快取剛結束週期的上帶、下帶與 VWAP 值（於重置前一根取樣）。當圖表來到最後一根 K 棒時，這些快取值會被一次性繪製為靜態箱型、一條虛線 VWAP 線與三個標籤——之後不再更新，是固定快照而非即時序列。
滾動 VWAP——與錨定 VWAP 不同，此路徑使用 PineCoders ConditionalAverages 函式庫，在固定的回看時間窗（天數換算為毫秒）內加總 price×volume、volume 與 volume×price²，每根 K 棒重新計算：VWAP = Σ(price·volume)/Σvolume，變異數 = Σ(volume·price²)/Σvolume − VWAP²（下限為零），σ = √變異數。Standard 模式下，帶線 = VWAP ± 倍數×σ；Symmetrical 模式下，帶線 = VWAP ± (倍數/100)×VWAP——為一個固定百分比包絡，而非統計性帶線。
聚合成交量——啟用時，腳本會透過 request.security 從最多四個獨立設定的標的抓取成交量並加總，取代僅使用目前圖表自身的成交量，再送入上述滾動 VWAP 公式。此設計是為了成交量分散於多個交易場所的商品（預設四個欄位指向同一加密貨幣交易對在四家交易所的成交量），但欄位可改為任何標的代碼。
初始平衡——逐根 K 棒比較兩個東京時區時段窗口：一個 1 小時的開盤區間（09:00–10:00），在其開始時決定箱型的高低點；以及涵蓋整個時段的 09:00–15:00 區間，箱型的右緣會延伸至此範圍內。一個滾動陣列僅保留最近 N 個日箱型（依所設定天數），超過上限時刪除最舊的箱型。
警報——每個警報於每根 K 棒收盤時最多觸發一次，格式為：VWAP+｜{標的} {時框} {價格}｜{事件名稱}。
🔶 設定說明
🔹 背景模式
背景模式 ：黑色背景（預設）／白色背景／自訂。黑色與白色背景會將所有 VWAP、帶、前期標記與 IB 框的顏色鎖定為對應該背景的固定配色，此時下方各條線的顏色設定不生效；切到自訂則解除鎖定，完全依你為每條線分別設定的顏色顯示。
🔹 主要 VWAP 設定（VWAP1–VWAP5，五組獨立插槽）
VWAP1 / VWAP2 / VWAP3 / VWAP4 / VWAP5 ：啟用該插槽；五組預設皆為關閉。
錨定週期 ：日／週／月／季／年——設定該插槽 VWAP 的重置時機。
VWAP ：該插槽 VWAP 線的顏色。
Bands ：1 個標準差上下帶的顏色。
Fill ：帶線填色區域的顏色。
🔹 前期 VWAP 標記
前日 / 前週 / 前前週 / 前月 / 前前月 / 前季 / 前前季 / 前年 ：各自開關會將該已結束週期的 VWAP 通道（箱型＋線＋標籤）投影至圖表右側；預設皆為關閉。
顏色（各標記） ：設定該標記的箱型／線／標籤色調。
🔹 滾動 VWAP
7D / 30D / 90D / 365D ：啟用該滾動窗口插槽；四組預設皆為開啟。
天數 ：從預設清單（1/3/5/7/14/21/28/30/60/90/182/365 天）自由選擇該插槽的滾動窗口長度，與插槽標籤無關。
RVWAP ：該插槽滾動 VWAP 線的顏色。
Bands ：該插槽偏差帶的顏色。
Fill ：該插槽帶線填色區域的顏色。
🔹 滾動 VWAP 標準差帶
使用聚合成交量 ：合併下方勾選交易所的成交量計算滾動 VWAP，取代僅使用目前圖表的成交量。
偏差帶模式 ：Symmetrical（VWAP 上下對稱的百分比帶）或 Standard（統計標準差帶）。
倍數 ：調整帶寬（最小 0.5，以 0.5 為單位遞增）。
交易所 1 / 2 / 3 / 4 ：開關該標的成交量是否納入聚合計算。
標的欄位（交易所 1–4） ：設定每個交易所插槽所抓取的成交量標的，預設為同一交易對在四大交易所的成交量，可改為任何標的。
🔹 初始平衡區間
顯示 IB 區間 ：開關初始平衡箱型，以東京時段（09:00–15:00）繪製，其高低點由 09:00–10:00 的開盤區間決定。
天數 ：圖表上保留幾天的 IB 箱型，超過後自動刪除最舊的一個。
顏色 ：箱型邊框／填色色調。
🔹 警報
VWAP1–VWAP5 觸及 ：價格影線碰到該錨定 VWAP 即於當根 K 棒收盤時觸發一次，不分逼近方向（該 VWAP 需先啟用）。
7D/30D/90D/365D RVWAP 觸及 ：同樣的觸及邏輯，適用於每一組已啟用的滾動 VWAP。
🔶 免責聲明
本指標及其所產生之所有信號、標記與警報，僅供技術分析學習與研究參考，不構成任何形式之投資建議、財務建議、交易推薦或買賣邀約。金融市場交易涉及高度風險，投資人可能損失部分或全部本金。過去表現不代表亦不保證未來結果。使用本指標之任何交易決策均由使用者自行判斷並承擔完全責任，作者與發布平台不負任何法律責任。請充分了解市場規則與自身風險承受能力，必要時諮詢具備合法資質的專業財務顧問。
Wskaźnik
Wskaźnik
Gap MapGap Map is a price-action mapping tool that identifies true price gaps and tracks them as live zones on the chart.
A true gap is defined as:
* Gap Up: the current open is above the previous bar’s high.
* Gap Down: the current open is below the previous bar’s low.
This means the script does not draw every close-to-open gap. It only maps gaps where the new bar opens completely beyond the previous bar’s range.
1. Core Idea
Price gaps can leave visible areas on the chart where no trading occurred between two consecutive bars.
Gap Map highlights these areas as zones and keeps them active until price fully fills the gap.
The goal is to help users visually track:
* Open true gaps
* Partially filled gaps
* Fully filled gaps
* High-volume gap zones
* Historical fill behavior on the current chart
This is a mapping and analysis tool. It is not a buy/sell indicator and not a trading strategy.
2. What the Indicator Draws
When a valid true gap appears, the script draws a zone between the previous bar’s range and the current open.
For a Gap Up, the zone is drawn between:
Previous high → Current open
For a Gap Down, the zone is drawn between:
Current open → Previous low
The zone remains active until price fully fills the gap.
3. Gap Size Filter
The script includes a minimum gap size filter based on ATR.
Gap size is measured in ATR units:
Gap size / Previous ATR
This helps filter out very small gaps that may not be visually or analytically useful.
Users can reduce the threshold to show more gaps or increase it to focus only on larger gaps.
4. Partial Fill Behavior
The script can optionally shrink a gap zone when price partially fills it.
When this option is enabled, the zone adjusts to show only the remaining unfilled part of the gap.
This helps users see whether a gap is still fully open, partially filled, or already closed.
5. Full Gap Fill
A gap is considered fully filled when price reaches the full-fill level.
For a Gap Up, the gap is filled when price trades back to the previous high.
For a Gap Down, the gap is filled when price trades back to the previous low.
Filled zones can either be removed from the chart or kept as faded historical zones, depending on the user’s settings.
6. High-Volume Gaps
The script compares the gap bar’s volume with its average volume.
If the gap appears with volume above the selected relative-volume threshold, it is marked with a highlighted border.
These high-volume gaps are treated as breakaway candidates for review.
This does not mean the gap cannot fill. It only means the gap occurred with stronger-than-usual volume and may deserve additional attention.
7. Optional Statistics Table
The optional statistics table summarizes gap behavior on the current chart.
It can show:
* Number of true gap-up zones
* Number of true gap-down zones
* Percentage filled so far
* Median bars to fill
* Number of open gaps now
* High-volume gap fill statistics
The table is intended as historical context for the current symbol and timeframe.
It should not be interpreted as a forecast that future gaps must behave the same way.
8. How to Use
A practical workflow:
1. Add the indicator to a clean chart.
2. Keep the default ATR filter first.
3. Review open gap zones.
4. Check whether price is approaching a gap zone.
5. Use partial-fill behavior to monitor how much of the gap remains open.
6. Turn on the statistics table if you want historical fill context.
7. Combine the gap map with trend, volume, support/resistance, and broader market context.
8. Best Use Cases
Gap Map is most useful for markets that can create real gaps, such as:
* Stocks
* ETFs
* Indices
* Session-based futures
* Markets with clear open/close sessions
It is less meaningful on continuously traded markets where true session gaps are rare.
10. Important Notes
This script maps true gaps only.
It does not draw every close-to-open difference.
It does not predict that a gap must fill.
It does not provide entry or exit signals.
It does not measure order flow.
It does not execute trades.
High-volume gap highlighting is for visual review only, not a confirmation of direction.
11. Alerts
The script includes alert conditions for:
* New true gap up
* New true gap down
* Gap filled
Alerts are informational only. They do not confirm future price movement.
12. Limitations
Gap behavior can vary by symbol, timeframe, volatility regime, market structure, earnings events, news events, and liquidity conditions.
A gap zone can remain open for a long time.
A gap can be partially filled and then price can continue in the original direction.
Large high-volume gaps may behave differently from small low-volume gaps.
Historical fill statistics are calculated from the current chart’s own history and should be treated as context, not a guarantee.
13. Educational Disclaimer
This script is for educational and chart-analysis purposes only. It is not financial advice, investment advice, or a recommendation to buy or sell any financial instrument. Users are responsible for their own analysis, risk management, and trading decisions.
Wskaźnik
SMT Sniper Entry Engine [trade_w_samet]🎯 SMT Sniper Entry Engine
SMT Sniper Entry Engine is a structured correlated-market divergence and confirmation indicator designed to help traders study liquidity sweeps, SMT divergence, reclaim quality, pair correlation, external-range location, displacement, Fair Value Gap evidence, micro-structure confirmation, and permanent bar-close UP or DOWN signals through one coordinated workflow.
The script is built around one central idea:
An SMT divergence should not automatically become an entry signal.
Instead of treating every difference between two correlated markets as equally meaningful, the engine first identifies a one-market liquidity sweep, then evaluates reclaim behavior, ATR-normalized sweep depth, candle direction, rejection quality, range expansion, pair correlation, external-range location, and divergence separation before the SMT event is accepted.
A qualified SMT event still does not create an immediate final signal.
The accepted SMT event arms a temporary confirmation sequence.
The engine then waits for directional displacement, a confirmed break of the SMT candle, and the additional evidence required by the active Engine Preset before a permanent UP or DOWN label is printed.
The indicator includes:
• Automatic comparison-symbol selection for supported metals, indices, cryptocurrencies, forex majors, and common forex crosses
• Manual comparison-symbol mode
• Same-timeframe comparison-market data
• Closed-bar rolling liquidity references
• Current-bar-close SMT divergence detection
• Either-market sweep acceptance
• Same-bar liquidity reclaim validation
• ATR-normalized sweep-depth measurement
• Chart-candle direction filtering
• Rejection-close filtering
• Minimum range-expansion filtering
• Separate bullish and bearish 0–100 Base Quality Scores
• Log-return pair-correlation analysis
• External-range location filtering
• ATR-normalized divergence-separation analysis
• Separate bullish and bearish 0–100 Sniper Scores
• Standard, Sniper, and Elite Engine Presets
• A temporary eight-bar confirmation window
• Sequential evidence accumulation across separate closed candles
• Directional displacement confirmation
• SMT-candle break confirmation
• Fair Value Gap confirmation
• Micro-structure break confirmation
• ATR-buffered setup invalidation
• Setup expiration
• Directional SMT cooldown
• Final signal cooldown
• One final UP or DOWN signal per completed SMT sequence
• Minimal historical SMT markers
• Dotted historical SMT reference lines
• Blue UP and orange DOWN labels
• Adjustable UP / DOWN label size
• Signal-confirming FVG boxes
• Recent-only chart-object
• A premium bottom-right dashboard
• Static TradingView alert conditions
• Combined dynamic alert() support
• “Any alert() function call” compatibility
• Data Window diagnostics
• Confirmed-close permanent signals
• No pivot functions
• No future-bar confirmation
• No historical signal backplotting
The purpose of this script is to provide a structured way to study when a correlated-market divergence is supported by sufficient liquidity, correlation, location, reaction, and confirmation evidence.
It is not financial advice.
It is not an automated trading system.
It does not guarantee profitable trades.
It does not execute broker orders.
It does not calculate position size.
It does not include a built-in TP / SL trade-management engine.
It does not provide verified win-rate or profitability statistics.
It does not replace independent analysis, execution planning, or risk management.
━━━━━━━━━━━━━━━━━━━━━━
📌 OVERVIEW
━━━━━━━━━━━━━━━━━━━━━━
At a high level, SMT Sniper Entry Engine does the following:
• Selects a comparison market automatically or manually.
• Requests the comparison market’s open, high, low, close, and ATR data on the chart timeframe.
• Builds rolling liquidity references from already completed candles.
• Checks whether only one market swept its corresponding liquidity reference.
• Requires the sweeping market to reclaim the reference on the same completed candle.
• Measures sweep depth relative to ATR.
• Evaluates chart-candle direction.
• Evaluates the candle’s closing position.
• Evaluates minimum range expansion relative to ATR.
• Produces separate bullish and bearish 0–100 Base Quality Scores.
• Measures the relationship between chart and comparison-market returns.
• Evaluates whether bullish SMT appears near the lower portion of the external range.
• Evaluates whether bearish SMT appears near the upper portion of the external range.
• Measures how clearly the non-sweeping market held its own liquidity reference.
• Produces separate bullish and bearish 0–100 Sniper Scores.
• Applies Standard, Sniper, or Elite acceptance thresholds.
• Confirms a qualified SMT event only after the current candle closes.
• Arms a temporary sequential confirmation window.
• Accumulates displacement, SMT-candle break, FVG, and structure evidence.
• Invalidates the setup if price closes beyond the SMT extreme by the stored ATR buffer.
• Expires the setup when confirmation does not arrive inside the available window.
• Applies final signal cooldown protection.
• Prints a permanent blue UP or orange DOWN label only after every required condition is confirmed.
• Optionally draws the FVG associated with the final signal.
• Displays current engine state, comparison symbol, correlation, active score, and signal counts in the dashboard.
• Provides separate static alert conditions.
• Provides one combined dynamic final-signal alert workflow.
• Exposes internal diagnostic values through TradingView’s Data Window.
The indicator does not use machine-learning prediction.
Its scores are not probabilities.
Its signal counts are not wins and losses.
Its labels do not promise future direction.
The script is a rule-based educational framework that explains how a raw correlated-market divergence becomes an accepted, rejected, invalidated, expired, or finally confirmed setup.
━━━━━━━━━━━━━━━━━━━━━━
🧠 CORE IDEA
━━━━━━━━━━━━━━━━━━━━━━
The core idea behind SMT Sniper Entry Engine is that two markets with a meaningful positive relationship do not always take corresponding liquidity at the same time.
When one market trades beyond a prior liquidity reference while the other market holds its own reference, the difference can create an SMT divergence.
However, the divergence alone contains limited information.
A basic SMT event does not automatically explain:
• whether the sweep was meaningful relative to volatility
• whether the sweeping market reclaimed the reference
• whether the chart candle closed with directional rejection
• whether the candle range expanded enough to matter
• whether the selected markets remain sufficiently correlated
• whether the event occurred near a useful external-range location
• whether the non-sweeping market clearly held its own level
• whether price produced directional displacement afterward
• whether the SMT candle was actually broken
• whether an FVG or micro-structure break confirmed the reaction
• whether the setup remained valid during the confirmation window
• whether another recent final signal is still inside the cooldown period
The engine therefore uses a staged sequence:
comparison-market selection
→ closed-bar liquidity references
→ one-market sweep
→ same-bar reclaim
→ Base Quality Score
→ pair-correlation validation
→ external-range location
→ divergence-separation validation
→ Sniper Score
→ confirmed SMT event
→ temporary setup arming
→ sequential reaction evidence
→ invalidation or expiration control
→ permanent UP or DOWN signal
For bullish conditions, the engine studies prior-low liquidity, bullish rejection, lower external-range location, directional displacement, a close above the SMT candle high, and bullish confirmation evidence.
For bearish conditions, the same process is mirrored around prior highs.
The purpose is not to produce the largest possible number of signals.
The purpose is to make the acceptance process selective, visible, and understandable.
━━━━━━━━━━━━━━━━━━━━━━
🧩 WHY THIS SCRIPT IS NOT A SIMPLE BUY/SELL INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
SMT Sniper Entry Engine is not designed to be used as a blind signal generator.
A raw correlated-market divergence must move through multiple stages:
One market sweeps liquidity
→ the comparison market does not make the same sweep
→ the sweeping market reclaims its reference
→ sweep depth is evaluated
→ chart-candle direction is checked
→ rejection-close quality is checked
→ range expansion is checked
→ the Base Quality Score is calculated
→ pair correlation is checked
→ external-range location is checked
→ divergence separation is checked
→ the Sniper Score is calculated
→ the SMT event is accepted
→ the confirmation window opens
→ directional displacement is accumulated
→ the SMT candle must be broken
→ FVG and/or micro-structure evidence is accumulated
→ the setup must avoid invalidation
→ the setup must confirm before expiration
→ the final UP or DOWN label appears
Each module serves a different purpose.
The comparison engine defines the external market used for SMT analysis.
The liquidity engine identifies the one-market sweep.
The reclaim engine checks whether the liquidity event closed back inside the reference.
The Base Quality Score evaluates the completed SMT candle.
The Sniper Context Engine evaluates correlation, location, separation, and sweep quality.
The sequential confirmation engine evaluates what price does after the SMT event.
The invalidation and expiration controls remove setups that no longer satisfy the intended sequence.
The dashboard explains the current engine state.
This makes the script a coordinated SMT-confirmation workflow rather than a simple divergence marker.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ HOW THE SCRIPT WORKS
━━━━━━━━━━━━━━━━━━━━━━
The script operates through connected calculation stages.
First, the engine selects a comparison symbol.
Auto mode uses the built-in symbol matrix.
Manual mode uses the symbol selected by the user.
The comparison market is requested on the same timeframe as the chart.
= request.security(
comparisonSymbol,
timeframe.period,
,
gaps = barmerge.gaps_off,
lookahead = barmerge.lookahead_off,
ignore_invalid_symbol = true)
The request uses lookahead_off.
The engine then calculates rolling chart and comparison-market liquidity references while excluding the current candle.
float chartPriorLow = ta.lowest(low , referenceLookback)
float chartPriorHigh = ta.highest(high , referenceLookback)
float comparisonPriorLow = ta.lowest(comparisonLow , referenceLookback)
float comparisonPriorHigh = ta.highest(comparisonHigh , referenceLookback)
The default reference lookback is 12 bars.
A bullish divergence is possible when one market sweeps a prior low and the other market does not.
A bearish divergence is possible when one market sweeps a prior high and the other market does not.
The sweeping market must reclaim the level on the same completed candle.
The candidate is then evaluated through:
• ATR-normalized sweep depth
• chart-candle direction
• close location
• range expansion
• Base Quality Score
• pair correlation
• external-range location
• divergence separation
• Sniper Score
• directional cooldown
When the SMT event is accepted, the engine stores:
• setup direction
• SMT bar
• SMT extreme
• SMT reaction trigger
• current ATR
• Base Quality Score
• Sniper Score
• sequential evidence states
• first confirmed FVG coordinates
The engine then monitors the next closed candles.
A final signal is accepted only when the active preset’s required evidence is present and the setup has not invalidated or expired.
━━━━━━━━━━━━━━━━━━━━━━
🟢 BULLISH SMT LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A bullish SMT candidate begins at prior lows.
The engine checks the chart symbol and comparison market together.
A bullish sweep divergence exists when either:
• the chart symbol trades below its prior low while the comparison market does not trade below its corresponding prior low
• the comparison market trades below its prior low while the chart symbol does not trade below its corresponding prior low
The engine accepts a sweep from either market.
The sweeping market must reclaim the prior-low reference when reclaim validation is active.
The completed chart candle must also satisfy the active quality requirements.
The default Sniper profile evaluates:
• sufficient ATR-normalized sweep depth
• bullish chart-candle direction
• a close in the stronger portion of the candle
• minimum candle-range expansion
• minimum Base Quality Score
• minimum positive pair correlation
• location near the lower portion of the external range
• minimum divergence separation
• minimum Sniper Score
• directional SMT cooldown availability
bool bullishSmtEvent =
bullishRawSmtCandidate and
bullishSniperPass and
bullishCooldownPass
When the bullish SMT event is confirmed, the engine stores:
• the SMT low as the bullish invalidation extreme
• the SMT high as the bullish reaction-break trigger
• the current ATR
• the current Base Quality Score
• the current Sniper Score
The confirmation sequence then waits for:
• bullish displacement
• a close above the SMT candle high
• FVG and/or micro-structure evidence according to the active preset
The bullish SMT marker is context.
The final blue UP label is the completed signal.
━━━━━━━━━━━━━━━━━━━━━━
🔴 BEARISH SMT LOGIC
━━━━━━━━━━━━━━━━━━━━━━
A bearish SMT candidate begins at prior highs.
A bearish sweep divergence exists when either:
• the chart symbol trades above its prior high while the comparison market does not trade above its corresponding prior high
• the comparison market trades above its prior high while the chart symbol does not trade above its corresponding prior high
The sweeping market must reclaim the prior-high reference when reclaim validation is active.
The completed chart candle must also satisfy the active quality requirements.
The default Sniper profile evaluates:
• sufficient ATR-normalized sweep depth
• bearish chart-candle direction
• a close in the weaker portion of the candle
• minimum candle-range expansion
• minimum Base Quality Score
• minimum positive pair correlation
• location near the upper portion of the external range
• minimum divergence separation
• minimum Sniper Score
• directional SMT cooldown availability
When the bearish SMT event is confirmed, the engine stores:
• the SMT high as the bearish invalidation extreme
• the SMT low as the bearish reaction-break trigger
• the current ATR
• the current Base Quality Score
• the current Sniper Score
The confirmation sequence then waits for:
• bearish displacement
• a close below the SMT candle low
• FVG and/or micro-structure evidence according to the active preset
The bearish SMT marker is context.
The final orange DOWN label is the completed signal.
━━━━━━━━━━━━━━━━━━━━━━
💎 SMT QUALITY FILTER SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script calculates separate bullish and bearish Base Quality Scores.
The score evaluates the completed SMT candle and its underlying liquidity event.
Each score is limited to 0–100.
The components are:
Sweep Role — maximum 25 points
The event must contain a valid one-market liquidity sweep.
Only one market should take the corresponding prior high or prior low.
Reclaim — maximum 20 points
The sweeping market must close back inside its prior liquidity reference.
Sweep Depth — maximum 20 points
The distance beyond the reference is measured relative to the corresponding market’s ATR.
Chart Candle Direction — maximum 15 points
Bullish SMT prefers a bullish chart candle.
Bearish SMT prefers a bearish chart candle.
Rejection Close — maximum 10 points
Bullish SMT prefers the chart close toward the high of the candle.
Bearish SMT prefers the chart close toward the low.
Range Expansion — maximum 10 points
The chart candle’s total range is compared with chart ATR.
The total score structure is:
25 + 20 + 20 + 15 + 10 + 10 = 100 points.
Preset-dependent minimum Base Quality Scores are:
• Standard: 60
• Sniper: 75
• Elite: 85
The Base Quality Score is not a win rate.
It is not a probability.
It measures how closely the completed SMT event matches the engine’s liquidity and candle-quality framework.
━━━━━━━━━━━━━━━━━━━━━━
📏 VOLATILITY / ATR NORMALIZATION FILTER
━━━━━━━━━━━━━━━━━━━━━━
The indicator uses ATR normalization to compare distances across changing volatility conditions.
ATR normalization is applied to:
• chart-side sweep depth
• comparison-side sweep depth
• divergence separation
• displacement body size
• setup invalidation buffer
• chart-candle range expansion
Sweep depth is calculated in relation to the ATR of the market that performed the sweep.
For example:
Chart Sweep Depth = distance beyond chart reference / chart ATR.
Comparison Sweep Depth = distance beyond comparison reference / comparison ATR.
Preset-dependent minimum sweep depth is:
• Standard: 0.04 ATR
• Sniper: 0.10 ATR
• Elite: 0.18 ATR
The chart candle must also meet a minimum range-to-ATR requirement:
• Standard: 0.40 ATR
• Sniper: 0.60 ATR
• Elite: 0.85 ATR
The setup invalidation buffer is based on the ATR stored when the SMT event occurs.
The default buffer is 0.10 ATR beyond the SMT extreme.
ATR normalization helps reduce dependence on raw price units.
It does not make one configuration universal.
Different symbols, sessions, data feeds, and market conditions can still produce different behavior.
━━━━━━━━━━━━━━━━━━━━━━
🕯️ DISPLACEMENT QUALITY FILTER
━━━━━━━━━━━━━━━━━━━━━━
After an SMT event is accepted, the engine requires directional displacement before a final signal can appear.
A bullish displacement candle requires:
• a confirmed closed candle
• close above open
• body size of at least 0.45 ATR
• body-to-range ratio of at least 0.55
• upper wick no greater than 0.35 of the full candle range
A bearish displacement candle requires:
• a confirmed closed candle
• close below open
• body size of at least 0.45 ATR
• body-to-range ratio of at least 0.55
• lower wick no greater than 0.35 of the full candle range
bool bullishDisplacement =
barstate.isconfirmed and
close > open and
signalCandleBody >= chartAtr * displacementBodyAtr and
signalBodyRatio >= displacementBodyPercent and
bullishOppositeWickRatio <= maximumOppositeWickPercent and
bullishPreviousBreakPass
The bearish process is mirrored.
The previous-bar break option is disabled in the locked default engine.
The more important directional reaction requirement is the SMT-candle break.
Displacement confirms that the market produced a completed directional response after the SMT event.
It does not guarantee continuation.
━━━━━━━━━━━━━━━━━━━━━━
📊 REACTION STRENGTH FILTER
━━━━━━━━━━━━━━━━━━━━━━
The engine does not require every confirmation component to appear on the same candle.
Instead, reaction evidence can accumulate across separate closed candles inside the temporary confirmation window.
The engine tracks:
• displacement
• SMT-candle break
• Fair Value Gap
• micro-structure break
Bullish SMT-candle break:
• price must close above the stored SMT candle high
Bearish SMT-candle break:
• price must close below the stored SMT candle low
Bullish FVG:
• current low is above the high from two bars earlier
Bearish FVG:
• current high is below the low from two bars earlier
Bullish micro-structure break:
• current close exceeds the highest high from the previous five closed bars
Bearish micro-structure break:
• current close falls below the lowest low from the previous five closed bars
Evidence is persistent while the setup remains active.
For example:
SMT event
→ displacement appears
→ FVG appears later
→ structure break appears on another candle
→ final signal confirms
The active Engine Preset determines which accumulated evidence is required.
━━━━━━━━━━━━━━━━━━━━━━
🧼 CONFIRMED SIGNAL FILTER
━━━━━━━━━━━━━━━━━━━━━━
Permanent SMT events and final UP / DOWN labels wait for candle close.
The engine uses confirmed-bar checks for:
• raw SMT candidates
• final SMT acceptance
• displacement
• FVG detection
• micro-structure breaks
• setup invalidation
• final UP signals
• final DOWN signals
The comparison-market request uses lookahead_off.
Rolling liquidity references exclude the current candle.
No future candle is used to decide whether the current candle contains an SMT event.
No final signal is plotted back onto the original SMT candle after later evidence becomes available.
The confirmation opportunity is temporary.
The default window is eight bars.
The minimum delay is one bar after the SMT event.
If the active evidence does not complete in time, the setup expires.
Historical output can still change when:
• Engine Preset changes
• comparison symbol changes
• Auto or Manual mode changes
• chart symbol changes
• timeframe changes
• exchange or broker feed changes
• historical data is revised
• the loaded history range changes
Confirmed-close logic prevents unfinished-candle conditions from becoming permanent chart signals.
It does not mean all brokers or data feeds will produce identical historical output.
━━━━━━━━━━━━━━━━━━━━━━
🎯 ENTRY MODEL
━━━━━━━━━━━━━━━━━━━━━━
SMT Sniper Entry Engine uses a confirmed-signal entry model rather than a built-in broker-order model.
A final directional setup is created only when:
• a qualified SMT event exists
• the confirmation window is open
• the setup has not invalidated
• all preset-required evidence has been accumulated
• final signal cooldown is available
• the current candle is confirmed
The final signal reference is the close of the candle where the UP or DOWN label is printed.
For an UP setup:
• the label appears below the confirmed signal candle
• the signal represents completed bullish SMT confirmation
For a DOWN setup:
• the label appears above the confirmed signal candle
• the signal represents completed bearish SMT confirmation
The script does not automatically calculate:
• an entry line
• a stop-loss level
• take-profit targets
• position size
• account risk
• broker quantity
• trade outcome
The final signal-bar close can be used as an analytical reference.
It is not a guaranteed fill.
Users must define their own execution, invalidation, stop, target, and risk model.
━━━━━━━━━━━━━━━━━━━━━━
🔗 COMPARISON MARKET MODEL
━━━━━━━━━━━━━━━━━━━━━━
The indicator supports Auto and Manual comparison-symbol modes.
Auto mode recognizes common ticker text and assigns a predefined positively related market.
Built-in mappings include:
Metals
• XAU or GOLD → OANDA:XAGUSD
• XAG or SILVER → OANDA:XAUUSD
Indices
• NAS, US100, USTEC, NDX, or NQ → OANDA:SPX500USD
• SPX, US500, SP500, or ES → OANDA:NAS100USD
• US30, DJI, DOW, or YM → OANDA:SPX500USD
Cryptocurrencies
• BTC → BINANCE:ETHUSDT
• ETH → BINANCE:BTCUSDT
Forex majors
• EURUSD ↔ GBPUSD
• AUDUSD ↔ NZDUSD
• USDCAD ↔ USDCHF
• USDJPY → CADJPY
JPY crosses
• EURJPY ↔ GBPJPY
• AUDJPY ↔ NZDJPY
• CADJPY → USDJPY
• CHFJPY → EURJPY
EUR and GBP crosses
• EURAUD ↔ GBPAUD
• EURNZD ↔ GBPNZD
• EURCAD ↔ GBPCAD
• EURCHF ↔ GBPCHF
• EURGBP → GBPUSD
AUD and NZD crosses
• AUDCAD ↔ NZDCAD
• AUDCHF ↔ NZDCHF
• AUDNZD → NZDUSD
Auto mode is based on ticker-name recognition.
Broker symbols can include prefixes, suffixes, futures contract codes, or synthetic names that are not recognized by the built-in matrix.
When the chart symbol is not recognized, the engine can fall back to the Manual Comparison Symbol value.
The dashboard should therefore be checked before relying on Auto mode.
Manual mode allows the user to select the comparison market directly.
The current engine is designed for positively correlated relationships.
Selecting an inversely related market can make the correlation and SMT logic unsuitable.
━━━━━━━━━━━━━━━━━━━━━━
🎯 SNIPER SCORE MODEL
━━━━━━━━━━━━━━━━━━━━━━
The engine produces separate bullish and bearish Sniper Scores.
The Sniper Score evaluates broader context around the SMT event.
The maximum score is 100.
The structure is:
Base SMT Quality — maximum 35 points
The 0–100 Base Quality Score contributes 35% of its value.
Pair Correlation — maximum 25 points
Positive effective correlation contributes proportionally.
External-Range Location — maximum 20 points
Bullish SMT receives this component when it occurs below the active maximum bullish range position.
Bearish SMT receives this component when it occurs above the active minimum bearish range position.
Divergence Separation — maximum 10 points
The event receives this component when the non-sweeping market holds its reference by at least the required ATR-normalized distance.
Sweep Depth — maximum 10 points
A valid minimum sweep receives five points.
A sweep at least 1.5 times the minimum depth receives ten points.
Minimum accepted Sniper Scores are:
• Standard: 60
• Sniper: 78
• Elite: 88
Minimum positive pair correlation is:
• Standard: 0.35
• Sniper: 0.55
• Elite: 0.70
External-range requirements are:
Bullish maximum position
• Standard: 0.45
• Sniper: 0.33
• Elite: 0.25
Bearish minimum position
• Standard: 0.55
• Sniper: 0.67
• Elite: 0.75
Minimum divergence separation is:
• Standard: 0.00 ATR
• Sniper: 0.03 ATR
• Elite: 0.08 ATR
The Sniper Score is not a probability.
A score of 88 does not mean an 88% probability of success.
It measures rule-based confluence according to this script’s internal framework.
━━━━━━━━━━━━━━━━━━━━━━
📦 ACTIVE SMT / FVG VISUAL SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
The script separates SMT context from final signal confirmation.
Historical SMT visuals can include:
• a dotted line from the prior chart-side liquidity reference to the SMT candle
• a minimal bullish or bearish marker near the SMT event
The default historical visual system keeps recent objects only.
The default limits are:
• eight bullish SMT lines
• eight bullish SMT markers
• eight bearish SMT lines
• eight bearish SMT markers
• ten final signal labels
• six signal FVG boxes
Older visual objects can be removed when the corresponding recent-only limit is exceeded.
This is chart-object management.
It does not move a signal to another candle.
Final signal visuals include:
UP
• blue label
• white bold-italic text
• printed below the confirmed signal candle
DOWN
• orange label
• white bold-italic text
• printed above the confirmed signal candle
Signal FVG Box
• appears only when stored FVG evidence exists
• uses the FVG that participated in the active confirmation sequence
• extends 12 bars to the right
• uses a lightly shaded bullish or bearish fill
The FVG box is an analytical confirmation visual.
It is not a guaranteed support, resistance, entry, stop, or target zone.
━━━━━━━━━━━━━━━━━━━━━━
🚦 ONE ACTIVE SMT SETUP AT A TIME
━━━━━━━━━━━━━━━━━━━━━━
The script maintains one active pending SMT confirmation sequence at a time.
When a qualified bullish SMT event appears:
• the active setup direction becomes bullish
• the bullish SMT extreme and trigger are stored
• the evidence state is reset
When a qualified bearish SMT event appears:
• the active setup direction becomes bearish
• the bearish SMT extreme and trigger are stored
• the evidence state is reset
A newly accepted SMT event can therefore replace the currently stored pending setup state.
The active setup remains in memory until:
• the final UP signal confirms
• the final DOWN signal confirms
• the setup invalidates
• the setup expires
• another accepted SMT event overwrites the pending state
This design prevents multiple overlapping confirmation sequences from creating an unclear chart state.
It does not prevent the user from performing independent analysis on other markets or timeframes.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ SEQUENTIAL CONFIRMATION WINDOW HANDLING
━━━━━━━━━━━━━━━━━━━━━━
The default confirmation window is eight bars.
The final signal cannot appear on the original SMT candle because the minimum bars after SMT is one.
The engine monitors each completed candle inside the window.
Evidence can be accumulated in different orders.
For example:
SMT
→ displacement
→ SMT-candle break
→ FVG
→ final signal
or:
SMT
→ FVG
→ displacement
→ SMT-candle break
→ structure break
→ final signal
Preset behavior:
Standard
Uses Reactive confirmation.
Requires:
• displacement
• SMT-candle break
Sniper
Uses Confirmed confirmation.
Requires:
• displacement
• SMT-candle break
• FVG or micro-structure break
Elite
Uses Elite confirmation.
Requires:
• displacement
• SMT-candle break
• FVG
• micro-structure break
The engine does not use the historical high-low sequence inside a candle to simulate order execution.
It evaluates whether each closed candle satisfied a defined piece of evidence.
If the setup does not complete inside the window, it expires.
━━━━━━━━━━━━━━━━━━━━━━
🏷️ SMT SNIPER LABELS
━━━━━━━━━━━━━━━━━━━━━━
The indicator uses separate context and final-signal labels.
SMT Context Markers
The default SMT marker layout is Minimal.
Bullish SMT uses an upward marker.
Bearish SMT uses a downward marker.
The marker appears on the actual SMT confirmation candle.
Its tooltip can include:
• bullish or bearish SMT direction
• Sniper Score
• Base Quality Score
• effective pair correlation
• active comparison symbol
Final Signal Labels
The final labels display:
𝙐𝙋
or:
𝘿𝙊𝙒𝙉
UP uses a blue background.
DOWN uses an orange background.
The text is white.
Available final-label sizes are:
• Tiny
• Small
• Normal
• Large
• Huge
Normal is the default.
The UP tooltip can include:
• bullish SMT confirmation mode
• final stored Sniper Score
• final stored Base Quality Score
The DOWN tooltip contains the mirrored information.
The SMT marker and final signal label serve different purposes.
The SMT marker identifies the qualified correlated-market divergence.
The UP or DOWN label identifies the completed sequential confirmation.
━━━━━━━━━━━━━━━━━━━━━━
📍 SMT DISPLAY MODES
━━━━━━━━━━━━━━━━━━━━━━
The indicator operates directly on the main price chart.
The public Display settings provide control over:
Show SMT
Shows or hides historical SMT markers and reference lines.
Show UP / DOWN
Shows or hides final signal labels.
UP / DOWN Label Size
Controls the size of final UP and DOWN labels.
Show Signal FVG
Shows or hides the stored FVG box associated with a final signal.
Show Dashboard
Shows or hides the premium bottom-right dashboard.
The internal visual profile uses:
• Clean layout
• Recent Only historical display
• dotted SMT reference lines
• minimal SMT markers
• normal SMT marker size
• limited historical object counts
• no separate displacement circles by default
Input values are hidden from TradingView’s status line.
Diagnostic plots remain available in the Data Window without adding visible price-scale clutter.
━━━━━━━━━━━━━━━━━━━━━━
🧹 SETUP INVALIDATION
━━━━━━━━━━━━━━━━━━━━━━
Not every accepted SMT event remains eligible.
A bullish setup invalidates when a completed candle closes below:
SMT low − stored SMT ATR × 0.10.
A bearish setup invalidates when a completed candle closes above:
SMT high + stored SMT ATR × 0.10.
The ATR value is stored when the SMT event appears.
This keeps the invalidation buffer linked to the volatility present when the setup was created.
A setup can also fail to produce a final signal because:
• the confirmation window expires
• displacement never appears
• the SMT candle is not broken
• required FVG evidence does not appear
• required structure evidence does not appear
• the final signal cooldown is active
• a newly accepted SMT event replaces the pending state
The directional SMT cooldown is 15 bars.
The final signal cooldown is eight bars.
A rejected, invalidated, or expired pending sequence does not print a final UP or DOWN label.
━━━━━━━━━━━━━━━━━━━━━━
📟 DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━
The indicator includes a premium dashboard in the bottom-right corner of the chart.
The header displays:
trade_w_samet • SMT SNIPER
Current State
Possible states include:
• SCANNING MARKET
• BULLISH SMT DETECTED
• BEARISH SMT DETECTED
• BULLISH SETUP BUILDING
• BEARISH SETUP BUILDING
• UP SIGNAL CONFIRMED
• DOWN SIGNAL CONFIRMED
Comparison
Displays the active comparison symbol.
Correlation
Displays the current effective pair correlation.
Engine
Displays:
• STANDARD
• SNIPER
• ELITE
Pair Mode
Displays:
• AUTO
• MANUAL
Signal Score
When a relevant setup is active, the dashboard displays:
current Sniper Score / required Sniper Score.
When no setup is active, it displays:
NO ACTIVE SETUP.
UP / DOWN Counts
Displays the number of final confirmed UP and DOWN signals calculated on the loaded chart history.
Footer
Displays:
• BAR-CLOSE
• NON-REPAINT
• LIVE
The dashboard is not TradingView Strategy Tester.
It does not display:
• win rate
• profit factor
• expectancy
• drawdown
• net profit
• broker-verified results
UP and DOWN counts are signal counts only.
“LIVE” means the dashboard updates with the latest available script state.
It does not mean the script predicts unfinished intrabar outcomes.
━━━━━━━━━━━━━━━━━━━━━━
🚨 ALERT SYSTEM
━━━━━━━━━━━━━━━━━━━━━━
SMT Sniper Entry Engine includes static TradingView alert conditions for:
• Bullish SMT
• Bearish SMT
• UP
• DOWN
• Any Signal
• Any SMT
Bullish SMT
Triggers when a bullish SMT event passes the complete Base Quality and Sniper acceptance process.
Bearish SMT
Triggers when a bearish SMT event passes the mirrored acceptance process.
UP
Triggers when the bullish sequential confirmation process is complete.
DOWN
Triggers when the bearish sequential confirmation process is complete.
Any Signal
Combines final UP and DOWN conditions.
Any SMT
Combines bullish and bearish SMT conditions.
The script also includes dynamic alert() messages for final UP and DOWN signals.
Dynamic messages can include:
• product name
• direction
• chart ticker
• chart timeframe
• confirmed close price
• active comparison symbol
if enableAlerts
if buySignal
alert(
"SMT Sniper | UP | " +
syminfo.ticker +
" | " +
timeframe.period +
" | Close: " +
str.tostring(close, format.mintick) +
" | Comparison: " +
comparisonSymbol,
alert.freq_once_per_bar_close)
The DOWN dynamic message uses the mirrored format.
Dynamic final-signal alerts use once-per-bar-close frequency.
Alerts are monitoring tools.
They do not place, modify, or close broker orders.
━━━━━━━━━━━━━━━━━━━━━━
🔔 HOW TO USE ALERTS
━━━━━━━━━━━━━━━━━━━━━━
For separate static conditions:
1. Add SMT Sniper Entry Engine to the chart.
2. Open TradingView’s Create Alert window.
3. Select SMT Sniper as the condition.
4. Choose Bullish SMT, Bearish SMT, UP, DOWN, Any Signal, or Any SMT.
5. Select the desired notification method.
6. Use a confirmed-bar frequency where appropriate.
7. Test the alert before relying on it.
For one combined dynamic final-signal alert:
1. Enable Alerts in the indicator settings.
2. Open TradingView’s Create Alert window.
3. Select SMT Sniper.
4. Select Any alert() function call.
5. Configure the delivery method.
6. Test the UP and DOWN message format.
The combined dynamic alert sends final UP and DOWN events through one TradingView alert.
Static Any Signal also combines UP and DOWN conditions, but uses the static alertcondition() message.
When indicator settings, code, symbol, or timeframe are materially changed, an already-created TradingView alert can continue using the script snapshot stored when that alert was created.
Recreate alerts after important configuration changes.
Alert delivery can depend on:
• TradingView servers
• selected symbol
• selected timeframe
• market-data availability
• realtime feed status
• symbol session
• user alert configuration
• webhook or external-service availability
Creating an alert does not guarantee broker execution.
━━━━━━━━━━━━━━━━━━━━━━
🧪 HOW TO USE THE INDICATOR
━━━━━━━━━━━━━━━━━━━━━━
A practical workflow:
1. Add SMT Sniper Entry Engine to a standard candlestick chart.
2. Begin with Engine Preset set to Sniper.
3. Keep Comparison Symbol Mode on Auto for supported symbols.
4. Review the Comparison field in the dashboard.
5. If the automatic market is not appropriate, switch to Manual.
6. Select a positively related comparison market.
7. Keep Show SMT enabled while learning the setup sequence.
8. Observe the historical liquidity reference line.
9. Observe the minimal SMT marker.
10. Treat the SMT marker as context, not as the final signal.
11. Watch the dashboard state.
12. Wait for a blue UP or orange DOWN label.
13. Review the active Sniper Score and required threshold.
14. Review the correlation value.
15. Review the signal FVG box when one is available.
16. Use alerts for monitoring rather than blind execution.
17. Evaluate broader market structure independently.
18. Review session conditions, volatility, spread, and news risk.
19. Define personal entry, invalidation, stop, target, and position-size rules.
20. Test the exact symbol, timeframe, exchange, broker feed, and comparison pair personally used.
The indicator is designed for structured review.
It should not be treated as an automatic decision-maker.
━━━━━━━━━━━━━━━━━━━━━━
⚙️ SETTINGS REFERENCE
━━━━━━━━━━━━━━━━━━━━━━
The public settings menu is intentionally simplified.
Advanced thresholds remain locked inside the engine to reduce configuration clutter and preserve consistent preset behavior.
⚙️ Engine
Engine Preset
Selects:
• Standard
• Sniper
• Elite
Standard
Produces more accepted setups.
Uses Balanced Base Quality, Standard Sniper thresholds, and Reactive confirmation.
Sniper
The default profile.
Uses Strict Base Quality, Sniper context thresholds, and Confirmed evidence requirements.
Elite
The most selective profile.
Uses Elite Base Quality, Elite context thresholds, and the strictest sequential evidence requirement.
A stricter preset does not guarantee better trading results.
━━━━━━━━━━━━━━━━━━━━━━
🔗 Comparison Market
Comparison Symbol Mode
Auto
Uses the internal ticker-recognition matrix.
Manual
Uses the selected Manual Comparison Symbol.
Manual Comparison Symbol
Selects the external market used by the SMT engine.
This field is active only when Comparison Symbol Mode is Manual.
Use a positively related comparison market.
━━━━━━━━━━━━━━━━━━━━━━
🎨 Display
Show SMT
Shows or hides historical SMT reference lines and markers.
Show UP / DOWN
Shows or hides final signal labels.
UP / DOWN Label Size
Selects:
• Tiny
• Small
• Normal
• Large
• Huge
Normal is the default.
Show Signal FVG
Shows or hides the stored FVG box associated with a final signal.
Show Dashboard
Shows or hides the bottom-right premium dashboard.
━━━━━━━━━━━━━━━━━━━━━━
🔔 Alerts
Enable Alerts
Enables the script’s static alert conditions and dynamic alert() calls.
For one combined runtime UP / DOWN alert, create the TradingView alert using:
Any alert() function call.
All public input values use hidden status-line display.
Diagnostic values remain available through TradingView’s Data Window.
━━━━━━━━━━━━━━━━━━━━━━
🧠 WHAT MAKES THIS SCRIPT ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━
SMT divergence, liquidity sweeps, correlation, ATR, Fair Value Gaps, and structure breaks are familiar technical-analysis concepts.
These concepts are not unique by themselves.
The originality of SMT Sniper Entry Engine lies in the coordinated process applied to them:
automatic comparison-market selection
→ closed-bar rolling liquidity references
→ one-market liquidity sweep
→ same-bar reclaim
→ ATR-normalized Base Quality Score
→ log-return pair correlation
→ external-range location
→ ATR-normalized divergence separation
→ 0–100 Sniper Score
→ preset-driven SMT acceptance
→ temporary sequential confirmation
→ displacement evidence
→ SMT-candle break
→ FVG and micro-structure evidence
→ ATR-buffered invalidation
→ setup expiration
→ permanent UP or DOWN signal
→ recent-only visual management
→ static and dynamic alerts
→ premium diagnostic dashboard
Distinctive implementation features include:
• accepting a valid sweep from either market
• using rolling closed-bar references instead of pivot confirmation
• separating the SMT event from the final signal
• calculating separate Base Quality and Sniper Scores
• requiring positive pair correlation according to preset
• using preset-specific external-range thresholds
• measuring divergence separation relative to ATR
• accumulating confirmation evidence across separate candles
• storing the SMT candle as the reaction trigger
• storing ATR at the moment the setup is armed
• using different confirmation strictness for Standard, Sniper, and Elite
• limiting historical objects without relocating signals
• providing automatic comparison-market assistance with manual override
• supporting both static and combined dynamic alerts
• exposing detailed diagnostics through the Data Window
The script is not a simple combination of unrelated indicators.
Every module supports the same objective: determining whether a closed-bar SMT divergence has enough liquidity, correlation, location, reaction, and confirmation evidence to become a permanent final signal.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ IMPORTANT PRACTICAL NOTES
━━━━━━━━━━━━━━━━━━━━━━
Signal frequency depends on:
• Engine Preset
• chart symbol
• comparison symbol
• ticker naming
• timeframe
• session
• volatility
• pair correlation
• liquidity-reference structure
• sweep depth
• chart-candle quality
• external-range location
• divergence separation
• directional cooldown
• post-SMT displacement
• SMT-candle break
• FVG evidence
• micro-structure evidence
• final signal cooldown
• available history
• data provider
Standard can produce more setups.
Elite can produce substantially fewer setups.
Fewer signals do not guarantee better results.
The built-in Auto matrix uses predefined OANDA and BINANCE symbols.
The chart symbol can come from another broker or exchange.
Different feeds can produce:
• different highs and lows
• different candle closes
• different ATR values
• different liquidity sweeps
• different correlation readings
• different final signals
Manual mode can be used when comparison-feed consistency is important.
The current engine expects a positive relationship.
An inversely related comparison market should not be selected.
The dashboard’s UP and DOWN values are signal counts.
They are not wins and losses.
The Signal Score is a confluence score.
It is not historical accuracy.
The SMT marker is not the final signal.
The final UP or DOWN label appears after post-SMT confirmation.
Changing settings recalculates historical conditions.
Changing the comparison market can materially change the script’s output.
━━━━━━━━━━━━━━━━━━━━━━
⚠️ LIMITATIONS AND SHORTCOMINGS
━━━━━━━━━━━━━━━━━━━━━━
This script has important limitations:
It does not guarantee profitable trades.
It does not predict future price movement.
It does not execute orders.
It does not place broker stops.
It does not place take-profit orders.
It does not calculate position size.
It does not include spread.
It does not include commission.
It does not include slippage.
It does not include latency.
It does not model partial fills.
It does not model financing or swap.
It does not evaluate order-book conditions.
It does not evaluate news risk.
It uses bar-based OHLC data.
It does not reconstruct exact intrabar price sequence.
It assumes a positive comparison relationship.
Its automatic matrix cannot recognize every broker symbol.
Unsupported Auto symbols can use the Manual Comparison fallback.
Correlation can change over time.
A historically correlated pair can temporarily decouple.
A confirmed SMT divergence can fail.
A displacement candle can be followed by reversal.
An FVG can be filled immediately.
A micro-structure break can become a false break.
A high Base Quality Score can still fail.
A high Sniper Score can still fail.
The Signal Score is not a win probability.
The dashboard is not TradingView Strategy Tester.
Signal counts are not audited account performance.
The script does not provide verified profitability statistics.
The script does not provide broker-verified trade outcomes.
Alert delivery depends on TradingView and user configuration.
Changing settings changes historical calculations.
Changing symbol, exchange, session, timeframe, or feed can change signals.
Available history can affect rolling calculations.
Permanent final signals wait for candle close.
The final label can therefore appear later than a discretionary intrabar entry.
For these reasons, the indicator should be used as an educational decision-support tool, not as a standalone automated strategy.
━━━━━━━━━━━━━━━━━━━━━━
👤 WHO THIS SCRIPT MAY BE USEFUL FOR
━━━━━━━━━━━━━━━━━━━━━━
This script may be useful for traders who:
• understand basic SMT divergence
• compare positively related markets
• study liquidity sweeps and reclaims
• want more context than a raw SMT marker
• prefer confirmed-close signals
• want selective preset modes
• use displacement as confirmation
• use Fair Value Gap concepts
• use micro-structure breaks
• want automatic comparison-market assistance
• want a manual comparison override
• want transparent quality scoring
• want a compact public settings menu
• want a premium dashboard
• want separate SMT and final-signal alerts
• want one combined UP / DOWN dynamic alert
• want Data Window diagnostics
It may be less suitable for users who:
• want guaranteed signals
• want every raw SMT divergence displayed
• want a fully automated trading bot
• want built-in TP and SL management
• want verified Strategy Tester performance
• want inverse-correlation SMT analysis
• expect one comparison pair to work on every feed
• require tick-level execution modeling
• want signals before candle close
• expect a score to equal probability
• want the indicator to replace personal judgment
• expect alerts to execute broker orders automatically
━━━━━━━━━━━━━━━━━━━━━━
🧭 BEST PRACTICE SUGGESTIONS
━━━━━━━━━━━━━━━━━━━━━━
For the default selective profile:
• use standard candlesticks
• begin with Sniper preset
• keep Auto mode only when the dashboard comparison is appropriate
• use Manual mode for broker-specific comparison control
• select positively related markets
• keep Show SMT enabled while learning
• distinguish the SMT marker from the final signal
• wait for the final UP or DOWN label
• review the correlation value
• review the active Signal Score
• review external market structure independently
• consider session liquidity and volatility
• use personal stop placement
• use personal target planning
• use personal position sizing
• test alerts before depending on them
• test the exact symbol and timeframe personally used
For additional frequency:
• use Standard preset
Standard reduces:
• Base Quality requirements
• correlation requirements
• range-location restrictions
• divergence-separation requirements
• Sniper Score threshold
• final confirmation evidence
For additional selectivity:
• use Elite preset
Elite increases:
• minimum sweep depth
• rejection-close requirement
• minimum range expansion
• Base Quality threshold
• correlation threshold
• external-range restriction
• divergence-separation threshold
• Sniper Score threshold
• final evidence requirement
Always:
• wait for the candle to close
• verify the active comparison symbol
• use the SMT marker as context
• use the final signal as confirmation
• review broader structure independently
• review personal risk before any trade
• treat alerts as monitoring tools
• remember that every confirmed setup can fail
━━━━━━━━━━━━━━━━━━━━━━
🔓 PUBLICATION NOTE
━━━━━━━━━━━━━━━━━━━━━━
SMT Sniper Entry Engine is published as an educational correlated-market divergence and confirmation tool.
The purpose of this description is to explain:
• how the comparison market is selected
• how Auto and Manual modes differ
• which markets are included in the automatic comparison matrix
• how closed-bar liquidity references are calculated
• how a one-market sweep is identified
• how reclaim validation works
• how sweep depth is normalized by ATR
• how chart-candle direction and rejection quality are evaluated
• how the Base Quality Score is constructed
• how pair correlation is calculated and filtered
• how external-range location is evaluated
• how divergence separation is measured
• how the Sniper Score is constructed
• how Standard, Sniper, and Elite differ
• how a qualified SMT event arms the confirmation engine
• how the temporary confirmation window works
• how evidence is accumulated across separate closed candles
• how displacement is detected
• how the SMT-candle break is used
• how Fair Value Gap evidence is detected
• how micro-structure evidence is detected
• how setup invalidation works
• how setup expiration works
• when final UP and DOWN labels appear
• what the SMT markers and dotted reference lines represent
• what the signal FVG box represents
• what the dashboard displays
• what the static alerts contain
• how “Any alert() function call” works
• what diagnostic values are available in the Data Window
• how confirmed-close timing works
• what the engine does not simulate
• why familiar SMT concepts are organized into an original workflow
The script is designed to support structured analysis.
It does not promise profitable results.
It does not remove market risk.
It does not execute trades.
It does not calculate position size.
It does not provide a built-in TP / SL trade-management model.
It should not be used as a blind UP / DOWN system.
Repainting and Timing Disclosure
SMT Sniper Entry Engine is designed around confirmed-bar calculations.
Permanent SMT events and final UP / DOWN labels use barstate.isconfirmed.
The comparison-market request uses:
• barmerge.gaps_off
• barmerge.lookahead_off
Liquidity references use previous closed candles.
The current candle is excluded from the prior-reference calculation.
The script does not use:
• pivot-high functions
• pivot-low functions
• future-bar confirmation
• negative plot offsets
• historical signal backplotting
• later relocation of final signal labels
A final UP or DOWN signal appears on the candle where the complete confirmation sequence becomes valid.
It is not moved backward to the original SMT candle.
Historical drawing cleanup can delete older lines, markers, labels, or boxes when the recent-object limit is exceeded.
Deleting an old drawing is not repainting.
The original signal bar is not changed.
Historical results can still differ when:
• settings are changed
• comparison symbols are changed
• Auto or Manual mode is changed
• chart symbols are changed
• timeframes are changed
• broker or exchange feeds are changed
• historical data is revised
• available chart history is changed
Realtime behavior also depends on when TradingView receives the final data for the closing candle.
Confirmed-close design reduces unfinished-candle changes.
It does not eliminate market risk, data-feed differences, or alert-delivery limitations.
━━━━━━━━━━━━━━━━━━━━━━
🛡️ DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━
SMT Sniper Entry Engine is provided for educational and informational purposes only.
It does not constitute financial, investment, trading, legal, or tax advice.
No indicator can guarantee future results.
Markets are uncertain.
Correlation changes.
Liquidity changes.
Volatility changes.
Market structure changes.
Historical chart behavior does not ensure future performance.
Every user is responsible for their own:
• analysis
• validation
• comparison-market selection
• execution planning
• stop placement
• target planning
• position sizing
• risk management
• alert configuration
• trading decisions
• broker execution
• legal obligations
• tax obligations
The liquidity references, SMT markers, dotted lines, Base Quality Scores, Sniper Scores, correlation values, external-range filters, divergence-separation values, displacement conditions, Fair Value Gap boxes, micro-structure conditions, UP labels, DOWN labels, dashboard states, Data Window values, signal counts, and alerts are visual analysis tools only.
The SMT marker is not a guaranteed reversal.
The UP label is not a guaranteed profitable long trade.
The DOWN label is not a guaranteed profitable short trade.
The Signal Score is not a win probability.
The Base Quality Score is not a probability.
The correlation reading is not a guarantee that two markets will continue moving together.
The automatic comparison symbol is not guaranteed to be suitable for every broker feed.
The FVG box is not a guaranteed support or resistance zone.
The micro-structure break is not a guarantee of continuation.
The final signal-bar close is not a guaranteed fill.
The script does not include spread, commission, slippage, latency, financing, contract specifications, order rejection, partial fills, or broker-specific execution behavior.
Use this script as a structured SMT divergence-review and confirmation framework, not as a promise of profitability or a substitute for independent judgment.
Wskaźnik
