OPEN-SOURCE SCRIPT
Aktualisiert SMT Sniper Entry Engine [trade_w_samet]
🎯 SMT Sniper Entry Engine [trade_w_samet]
SMT Sniper Entry Engine [trade_w_samet] 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.
Pine Script®
The request uses lookahead_off.
The engine then calculates rolling chart and comparison-market liquidity references while excluding the current candle.
Pine Script®
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
Pine Script®
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
Pine Script®
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
Pine Script®
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 [trade_w_samet] 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 [trade_w_samet] 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 [trade_w_samet] 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 [trade_w_samet] 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.
SMT Sniper Entry Engine [trade_w_samet] 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.
[comparisonOpen, comparisonHigh, comparisonLow, comparisonClose, comparisonAtr] = request.security(
comparisonSymbol,
timeframe.period,
[open, high, low, close, ta.atr(atrLength)],
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[1], referenceLookback)
float chartPriorHigh = ta.highest(high[1], referenceLookback)
float comparisonPriorLow = ta.lowest(comparisonLow[1], referenceLookback)
float comparisonPriorHigh = ta.highest(comparisonHigh[1], 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 [trade_w_samet] 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 [trade_w_samet] 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 [trade_w_samet] 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 [trade_w_samet] 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.
Versionshinweise
🔄 Update — ATR-Based TP / SL Trade BoxesA new trade management system has been added to **SMT Sniper Entry Engine [trade_w_samet]**.
✅ New Features
* Automatic trade boxes are now created after confirmed **UP** and **DOWN** signals.
* Entry is calculated from the confirmed signal candle’s closing price.
* Stop Loss is calculated using ATR.
* Take Profit is fixed at **2R**.
* ATR Length can now be adjusted directly from the indicator settings.
* Default ATR Length is set to **14**.
* ATR Stop Loss Multiplier can also be customized.
* Only one trade can remain active at a time.
* Historical TP and SL boxes remain visible on the chart.
* TP HIT and SL HIT result labels have been added.
* New TP and SL alert conditions are now available.
🛡️ Conservative Trade Evaluation
If both TP and SL are touched during the same candle, the engine records the Stop Loss first. This conservative calculation method helps prevent unrealistic or overstated historical results.
🔒 Core Logic Preserved
No changes were made to:
* SMT divergence detection
* Sequential confirmation logic
* Displacement confirmation
* FVG and structure-break evidence
* Setup invalidation
* UP and DOWN signal generation
* Non-repaint bar-close confirmation
* Existing dashboard and alerts
This update adds structured risk management without changing the original SMT signal engine.
Educational use only. Not financial advice.
Open-source Skript
Ganz im Sinne von TradingView hat dieser Autor sein/ihr Script als Open-Source veröffentlicht. Auf diese Weise können nun auch andere Trader das Script rezensieren und die Funktionalität überprüfen. Vielen Dank an den Autor! Sie können das Script kostenlos verwenden, aber eine Wiederveröffentlichung des Codes unterliegt unseren Hausregeln.
Clean indicators & Systems 💻
Free & PRO+ tools, setup guides & books.➡️
🌐 tradewsamet.com
whop.com/joined/tradewsamet
Free & PRO+ tools, setup guides & books.➡️
🌐 tradewsamet.com
whop.com/joined/tradewsamet
Haftungsausschluss
Die Informationen und Veröffentlichungen sind nicht als Finanz-, Anlage-, Handels- oder andere Arten von Ratschlägen oder Empfehlungen gedacht, die von TradingView bereitgestellt oder gebilligt werden, und stellen diese nicht dar. Lesen Sie mehr in den Nutzungsbedingungen.
Open-source Skript
Ganz im Sinne von TradingView hat dieser Autor sein/ihr Script als Open-Source veröffentlicht. Auf diese Weise können nun auch andere Trader das Script rezensieren und die Funktionalität überprüfen. Vielen Dank an den Autor! Sie können das Script kostenlos verwenden, aber eine Wiederveröffentlichung des Codes unterliegt unseren Hausregeln.
Clean indicators & Systems 💻
Free & PRO+ tools, setup guides & books.➡️
🌐 tradewsamet.com
whop.com/joined/tradewsamet
Free & PRO+ tools, setup guides & books.➡️
🌐 tradewsamet.com
whop.com/joined/tradewsamet
Haftungsausschluss
Die Informationen und Veröffentlichungen sind nicht als Finanz-, Anlage-, Handels- oder andere Arten von Ratschlägen oder Empfehlungen gedacht, die von TradingView bereitgestellt oder gebilligt werden, und stellen diese nicht dar. Lesen Sie mehr in den Nutzungsbedingungen.