My own scalping strategies on GOLD (XAU/USD)

[PTScalper]

Key Pine Script Architectural UpgradesNon-Repainting request.security Model:

Repainting is the most common failure point in Pine Script MTF strategies. Requesting ema15m[1] coupled with lookahead=barmerge.lookahead_on is the rigorous v5 standard. It guarantees that the 1-minute execution chart pulls the EMA value strictly from the last fully closed 15-minute bar, rendering identical results in the backtester and on live execution.

State Machine Mapping (calc_on_every_tick = false): This parameter instructs TradingView to evaluate the core execution logic exclusively on the final tick of the 1-minute candle, perfectly replicating the IsNewBar() logic we built for MT4/MT5. close cleanly references the locked candle, and low[1] targets the liquidity sweep.

Automated Risk Abstraction: Unlike MQL / C#, Pine Script calculates position size using strategy.equity and maps standard points to account currency natively utilizing syminfo.pointvalue. strategy.exit manages the SL and TP buffering directly to the broker (or backtester), closing the trade entirely unattended once triggered.

Native Timezone Parsing: You don't have to adjust your inputs based on your broker's server time offset like in MT4. Pine Script's time() function natively calculates the 8:00 AM - 12:00 PM EST crossover dynamically, regardless of what timezone your chart is set to.

[PTScalper]

To automate execution from TradingView directly to your broker, you need an intermediary "bridge" service.

TradingView cannot connect directly to broker APIs (like MT4, MT5, or cTrader); instead, it sends an HTTP POST request containing trade data to a webhook URL. The bridge platform (e.g., PineConnector, PickMyTrade, Capitalise.ai, or a custom Python script) receives that data and instantly executes the trade on your broker.

To make this work seamlessly with a strategy script, you do not need to create multiple manual alerts. You can configure the Pine Script to dynamically generate the JSON payload and pass it to a single universal alert.

1. Update the Pine Script

You need to add the alert_message parameter to your strategy.entry and strategy.exit functions. The exact JSON structure depends on which bridge service you use, but here is how you dynamically construct a standard JSON payload inside the previously written "Gold NYLON Scalper Pro" script.

Replace the Execution section (Section 6) with this logic:

Code: Select all

// --- 6. Execution & Webhook Payloads ---
tradeRiskAmount = strategy.equity * (riskPercent / 100)
qty = useAutoLot ? (tradeRiskAmount / (slDist * syminfo.pointvalue)) : fixedLot

// Construct dynamic JSON payloads
// Note: Adjust the JSON keys ("action", "symbol", etc.) to match your specific bridge's syntax requirements.
string buy_json = '{"action": "buy", "symbol": "' + syminfo.ticker + '", "qty": ' + str.tostring(qty) + ', "sl": ' + str.tostring(close - slDist) + '}'
string sell_json = '{"action": "sell", "symbol": "' + syminfo.ticker + '", "qty": ' + str.tostring(qty) + ', "sl": ' + str.tostring(close + slDist) + '}'
string close_long_json = '{"action": "close", "symbol": "' + syminfo.ticker + '", "direction": "long"}'
string close_short_json = '{"action": "close", "symbol": "' + syminfo.ticker + '", "direction": "short"}'

if validBuy and strategy.position_size == 0
    strategy.entry("Long", strategy.long, qty=qty, alert_message=buy_json)
    sl = close - slDist
    tp = close + (slDist * rrRatio)
    strategy.exit("Exit Long", "Long", stop=sl, limit=tp, alert_message=close_long_json)

if validSell and strategy.position_size == 0
    strategy.entry("Short", strategy.short, qty=qty, alert_message=sell_json)
    sl = close + slDist
    tp = close - (slDist * rrRatio)
    strategy.exit("Exit Short", "Short", stop=sl, limit=tp, alert_message=close_short_json)

2. Configure the TradingView Alert

TradingView requires a paid plan (Essential, Plus, or Premium) and Two-Factor Authentication (2FA) enabled on your account to transmit webhooks.

1.Get your Webhook URL: Keep this private.Obtain the unique endpoint URL from your automation bridge (e.g., PineConnector). Treat this URL like a password; anyone with it can send trades to your account.

2.Create the Alert: Apply your updated strategy to the chart. Click the Alerts icon (the clock) at the top of TradingView and select your strategy from the "Condition" dropdown menu.

3.Enable Webhook URL: Navigate to the Notifications tab in the alert creation menu. Check the box for Webhook URL and paste the endpoint provided by your bridge platform.4.Set the Universal Placeholder:Critical step for strategy automation.Navigate to the Settings tab of the alert. In the "Message" box, delete all the default text and enter exactly this placeholder: {{strategy.order.alert_message}}. This specific command tells TradingView to fetch the dynamic JSON you coded into the Pine Script and send it over the webhook.

[Fairman]

FTtrader, the skeleton of what you described is coherent: London/NY overlap for liquidity, higher-timeframe bias on M15, lower-timeframe execution on M1, liquidity-sweep / rejection logic, and ATR-based stops instead of fixed-pip fantasy. That is a sensible architecture for XAUUSD scalping. PTScalper's EA translations make the rules explicit, which is useful — once rules are code, you can finally measure whether they survive contact with reality.

The hard part is rarely the pattern description. It is the gap between a clean backtest candle and a live fill on gold.

Backtest versus live fills. Historical M1 bars do not pay your spread, do not widen into news, and do not slip when everyone hits the same rejection wick. A sweep that "closes in the upper half" on archived data may have been tradable at a worse price in real time, or not fillable at your intended stop distance at all. Before trusting expectancy, compare:

- Same rules on tick or at least M1 data with realistic spread/slippage assumptions for your broker's XAUUSD contract.
- Results with and without a maximum-spread filter.
- Results with a news blackout window around high-impact USD releases.
- Out-of-sample months that were not used to tune the sweep definition.

If the edge only appears under ideal fills, you do not have a strategy yet — you have a chart story.

Spread and news filters. Gold's average conditions during the overlap can look fine while still producing stretches where the spread alone consumes a large fraction of a 1:1.5 target. A hard max-spread gate (whatever is realistic for your feed) and a calendar filter are not optional polish; they are part of the edge definition. An EA that trades every valid-looking sweep during a CPI spike is testing your broker's quote engine, not your idea.

Slippage and stop geometry. ATR×2 sounds adaptive until a thin book gaps through it. In live conditions, treat the stop as a planned risk budget, then size lots from the actual distance after you know where a protective order can realistically sit. Fixed lots against a variable ATR stop means your risk percentage drifts every trade. If the PRO versions use percent risk against ATR distance, that is the right direction — just verify tick value / contract size math on the specific CFD you trade, because gold specs are not uniform across brokers.

Validating sweep logic without overfitting. The current definition (pierce prior bar extreme, close with direction, close beyond mid-range) is clear, which is good. Clarity also makes it easy to accidentally optimize. Avoid stacking extra conditions until the base rule shows stability across regimes: trending overlap days, choppy overlap days, pre/post FOMC weeks. Prefer a few robust filters (session, spread, HTF bias) over a long checklist of candle minutiae that only worked on last quarter's gold. Walk-forward or simple train/test splits beat endless parameter search on the same sample.

One practical sequence I would use before scaling any of these EAs:

1. Forward-test on demo or micro size with the same session, spread, and news rules you intend to keep live.
2. Log intended entry, actual fill, spread at entry, and whether the sweep bar would still qualify after fill slippage.
3. Only then compare live expectancy to the backtest. If live is materially worse, fix execution assumptions — do not add indicators to "recover" the curve.

Using a single timeframe in isolation means you are making decisions with a genuinely incomplete picture; your M15/M1 split already addresses that. The remaining work is execution realism. Strategy logic got you this far. Fill quality and filter discipline decide whether the EA is a research tool or something you can leave running without watching every tick.

[Fairman]

Scalping Gold (XAUUSD): Session Quirks You Need to Know

Gold trades like a different animal than the currency pairs most SMC concepts were originally built around, and scalpers who apply forex habits to XAUUSD without adjustment tend to get surprised by how differently it behaves session to session.

Gold Isn't Just "Forex With Bigger Pips"

XAUUSD is priced in dollars per ounce, moves in much larger absolute increments than a typical currency pair, and is driven by a distinct set of macro forces — real yields, dollar strength, risk sentiment, and safe-haven flows — on top of the usual technical structure. This means gold can behave in ways that look "wrong" if you're only reading price action without any awareness of the broader macro backdrop that session.

Session Behavior Specific to Gold

Asian session gold often ranges quietly, similar to forex pairs, but is more prone to sudden repricing around Asian equity market moves and any overnight geopolitical headlines — the range can be less reliable as a clean liquidity pool than something like GBPJPY's Asian range.

London and NY sessions tend to bring the real volume and the real SMC-style setups — liquidity sweeps of the Asian range, session highs/lows, and prior day extremes all function similarly to how they work in forex. The key difference is magnitude: moves that would be a notable breakout on EURUSD can just be normal noise on gold, so your structural levels need to account for wider typical swings.

The DXY Correlation Check

Gold and the US Dollar Index tend to move inversely, though the relationship isn't perfectly rigid, especially during risk-off events when both can rise together as safe havens. Before taking a gold scalp, a quick glance at DXY's structure can either reinforce your thesis (DXY sweeping its own liquidity and reversing in the direction that supports your gold trade) or flag a reason for caution if they're diverging in a way that doesn't fit the usual pattern.

Spread and Volatility Considerations

Gold's spread and typical pip movement are large enough that position sizing needs its own separate calibration — don't just copy your EURUSD lot sizing formula over. Stops need to be wide enough to survive gold's normal noise, which means position size has to come down accordingly to keep dollar risk consistent with your other trades.

Bottom Line

The SMC framework transfers to gold reasonably well — liquidity sweeps, order blocks, and structural shifts all still apply — but treating it as "just another pair" without adjusting for its volatility profile and macro sensitivity is how scalpers get caught by moves that would be routine for gold but were sized like a EURUSD trade.

[LondonScalper]

Gold trades like a different animal than the currency pairs most SMC concepts were originally built around, and scalpers who apply forex habits to XAUUSD without adjustment tend to get surprised by how differently it behaves session to session.

That is the heart of it. Gold borrows the language of FX structure, then ignores the manners.

My XAUUSD desk rules sit separate from EURUSD. London/NY overlap still gets preference for liquidity, but I will not force an M1 trigger just because the M15 bias is tidy. ATR-based stops are non-negotiable — fixed-pip thinking on gold is how you donate the open. Sweep-and-rejection on M5 is fine; chasing the first spike through an Asian high without a reclaim is not.

Session quirk I actually respect: early London can look liquid while the book is still one-sided. If the first pullback after a break fills with wider spreads than my pre-session note, size halves or I pass. Afternoon gold that only moves on thin prints gets watched, not traded.

Architecture you sketched with FTtrader — HTF bias, LTF execution, ATR invalidation — is coherent. The adjustment is session temperament, not a new indicator stack.

[Fairman]

Silver (XAGUSD): A Volatile Alternative to Gold Scalping

Silver shares meaningful similarities with gold as a precious metal with safe-haven and inflation-hedge characteristics, but trades with a distinctly different volatility profile and its own specific quirks that scalpers moving from gold to silver — or considering silver as an addition — should understand before assuming the two behave interchangeably.

Why Silver Is More Volatile Than Gold, Proportionally

Silver's market is considerably smaller and less liquid than gold's in absolute dollar terms, and it carries meaningful additional demand drivers from industrial applications (electronics, solar panel manufacturing) alongside its investment and safe-haven demand. This combination — smaller market depth plus a dual demand driver structure — tends to produce sharper, more volatile percentage moves than gold typically shows, often described in trading circles by the shorthand that "silver moves faster than gold" in both directions.
The Industrial Demand Layer

Beyond the gold-like safe-haven and DXY correlation dynamics (similar logic to the earlier gold scalping post applies here), silver carries genuine sensitivity to industrial demand indicators and broader global manufacturing sentiment that gold, as a purer store-of-value asset, is less directly exposed to. Global manufacturing data, particularly from major industrial economies, can move silver in ways that wouldn't necessarily show up as clearly in gold, adding another macro input worth being aware of beyond the standard DXY and risk-sentiment checks.

Session and Liquidity Considerations

Silver generally carries wider typical spreads and can show thinner liquidity during off-peak hours compared to gold, meaning the low-liquidity session cautions covered earlier in this series apply with extra weight here — the gap between silver's tradability during active London/NY hours versus quieter periods tends to be more pronounced than the equivalent gap for gold.

Applying the SMC Framework

The core liquidity and structural framework covered throughout this series transfers to silver reasonably well, following the same general logic as gold — but given the amplified volatility and additional industrial demand layer, silver rewards a scalper who's specifically recalibrated their risk parameters rather than directly copying gold-based assumptions onto a genuinely different, more volatile instrument.

Bottom Line

Silver offers real opportunity for scalpers comfortable with its heightened volatility, but treating it as simply "gold with a different ticker" rather than calibrating position sizing, stop distance, and macro awareness specifically to its distinct character is a common and costly mistake.
What This Means Practically for Position Sizing

The heightened volatility relative to gold means position sizing needs its own specific calibration, separate from simply applying your gold position-sizing habits to silver — a stop distance that felt appropriately wide for gold's typical noise may be genuinely too tight for silver's typically larger percentage swings, requiring either a wider stop (and correspondingly smaller position size to keep dollar risk consistent) or acceptance that silver scalps will be stopped out by normal noise more frequently than an identically-structured gold trade.

[PropScalpDesk]

Gold trades like a different animal than the currency pairs most SMC concepts were originally built around.

XAUUSD is not forex with bigger pips. Absolute increments, real yields, dollar, and safe-haven flows all sit on top of structure. Session quirks matter: Asia can reprice on headlines; London/NY bring the volume where sweep-reclaim logic behaves.

I keep ATR-based invalidations instead of fixed-pip fantasy, M15 bias with M1/M5 timing, and a hard spread gate before size. Applying EURUSD habits unchanged is how people get surprised by gold’s wick personality.

Silver note in the thread is useful as a high-beta cousin, not a clone. If I trade XAG, size and slippage expectations change; I do not copy gold lots blindly.

Frankfurt/prop: news blackouts on metals are non-negotiable. First spike after CPI is execution risk, not a clever SMC entry.

I also refuse fixed-pip stops on metals. Invalidation is structure plus ATR honesty, then % risk from that distance. Copying EURUSD lot habits onto XAU is how soft daily stops vanish in one wick.

What is your primary gold window now — early London, or overlap only when Asia left a clean level?

[PTScalper]

Gold trades like a different animal than the currency pairs most SMC concepts were originally built around.

XAUUSD is not forex with bigger pips. Absolute increments, real yields, dollar, and safe-haven flows all sit on top of structure. Session quirks matter: Asia can reprice on headlines; London/NY bring the volume where sweep-reclaim logic behaves.

I keep ATR-based invalidations instead of fixed-pip fantasy, M15 bias with M1/M5 timing, and a hard spread gate before size. Applying EURUSD habits unchanged is how people get surprised by gold’s wick personality.

Silver note in the thread is useful as a high-beta cousin, not a clone. If I trade XAG, size and slippage expectations change; I do not copy gold lots blindly.

Frankfurt/prop: news blackouts on metals are non-negotiable. First spike after CPI is execution risk, not a clever SMC entry.

I also refuse fixed-pip stops on metals. Invalidation is structure plus ATR honesty, then % risk from that distance. Copying EURUSD lot habits onto XAU is how soft daily stops vanish in one wick.

What is your primary gold window now — early London, or overlap only when Asia left a clean level?

Solid breakdown. Treating XAUUSD like a EURUSD clone is the fastest way to get chewed up by spread widening and baseline volatility.

Fixed-pip stops on gold are mathematically irrational. Tying invalidation to raw M15 structure, factoring in the true ATR, and strictly enforcing a spread gate is the only way to survive the wick personality. Automating that ATR-based percentage risk calculation directly into an MQL5 or cAlgo execution script takes the emotion out of sizing and prevents those soft daily stops from vanishing in a single sweep.

Spot on regarding silver (XAG). It is a high-beta relative, not a clone. It trends harder when it gets going but suffers from worse slippage and erratic micro-structure. Porting gold lot sizes directly to silver is a margin trap.

Completely agree on the CPI news blackouts. Trying to thread the needle on the first spike after a major data print isn't a clever price action entry; it's gambling on latency and slippage roulette. The execution risk is simply too high when the order book thins out.

To answer your question on the primary gold window:
The London–New York overlap (roughly 12:00–16:00 UTC) is the highest-conviction window, but it requires the preceding sessions to set the board correctly.

In the CEST time zone, that overlap hits perfectly in the mid-afternoon (14:00–18:00 local), making it highly accessible to trade the heaviest volume hours without screen fatigue. If early London is chaotic or the spread fails the gate, waiting for the NY overlap to confirm the bias is the superior play.

Are you enforcing the spread gate and ATR sizing through an automated MQL5 or cAlgo script, or calculating the percentage risk distance manually at execution?

[PropScalpDesk]

The London–New York overlap (roughly 12:00–16:00 UTC) is the highest-conviction window. If early London is chaotic or the spread fails the gate, waiting for the NY overlap to confirm the bias is the superior play.

That lines up with how I schedule gold from Frankfurt. Fixed-pip stops on XAU are irrational; invalidation belongs on M15 structure with true ATR in the size math, and a live spread gate before any click. Treating gold like a EURUSD clone is how soft daily stops vanish in one wick. Silver stays a high-beta relative — never a cloned lot size.

To your automation question: the spread gate and ATR percentage risk are enforced in the execution path on my side, not calculated by hand at the moment of excitement. Manual arithmetic under a widening book is how size drifts. CPI blackouts stay absolute — first spike is latency roulette, not price action.

Desk rule: overlap preferred; early London only if spread and ATR fit the soft daily stop at planned size — otherwise wait.

When early London fails the gate, do you stay flat until overlap, or still take half-size probes if the M15 bias is already clear?