GOLD DIGGA PRO
Two measured sleeves for gold, on the 15-minute chart. A diamond only where a sleeve places an order.
GOLD DIGGA PRO with ZONE DIGGA and REGIME DIGGA beside it: €20/mo, or €143/yr billed annually. 10-day free trial.
GOLD DIGGA PRO ver2.0 runs two sleeves, both measured on gold: Scalps, order-block limit entries on 15-minute XAUUSD (and the gold futures MGC / GC), and the Regular, the overnight-range breakout on 15-minute charts. The two sleeves are independent, so both can hold a trade at the same time. A diamond appears only where a sleeve places an order, and the chart follows each order to its fill and exit.
On OANDA:XAUUSD 15m, 1 January 2022 → 17 May 2025, Scalps made 167 trades, +42.8R, profit factor 1.374, on data it was not tuned on. The Regular, January 2010 → October 2026, net of a $0.30/oz spread: 4,264 trades, PF 1.14, maximum drawdown 23.7R. It earned in the years gold trended; before 2010 the rule lost.
You control how it looks and which sleeves alert you. How each sleeve decides was measured, and stays fixed. GOLD DIGGA PRO ULTRA, included with PRO, runs the same sleeves as a TradingView strategy, so you can check the published numbers in the Strategy Tester on your own chart.
What you get
- Two sleeves on 15-minute gold — Scalps (spot XAUUSD or MGC / GC) and the overnight-range Regular
- A diamond means an order — the chart replays the backtest's own order logic, fill to exit
- A trade card on every diamond — entry, stop, exit and the position size for your risk
- One alert per chart carrying every event — order, fill, exit, with the R
- A bad-run warning for Scalps — information only, signals are never muted
- Runs on any symbol — off gold a red box says the result is unmeasured, and a setting hides it
- Visual customisation of every colour, box and label
What it did, and what it did not.
Every configuration measured on its own, and then run again on years no tuning decision ever touched. 1 of 7 held. The ones that did not are here too, ranked by that second column rather than the first — which is the only order that cannot be gamed.
| Tuning window | Never tuned on | |||||
|---|---|---|---|---|---|---|
| Configuration | Net | PF | Net | PF | Trades | Verdict |
| Gold Scalps 15m Jan 2022 – May 2025 | +29,700 | 2.22 | +47,090 | 1.371 | 183 | held |
| Gold Regulars 5m Jan 2022 – May 2025 | +21,500 | 2.24 | +37 | 1.001 | 67 | flat |
| Gold Regulars 15m Jan 2022 – May 2025 | +13,100 | 2.66 | −1,322 | 0.931 | 25 | flat |
| MGC Magic v1 15m Jan 2022 – Aug 2025 | +38,800 | 3.09 | −2,597 | 0.959 | 91 | flat |
| MGC Scalp v1 5m May 2022 – Aug 2024 | +56,600 | 1.87 | −12,932 | 0.844 | 115 | lost |
| Gold Magic 5m Jan 2022 – May 2025 | +43,900 | 1.81 | −41,482 | 0.809 | 311 | lost |
| Gold Scalps 5m Jan 2022 – May 2025 | +25,100 | 2.76 | −53,791 | 0.534 | 135 | lost |
Fixed position sizing, $100,000 account, 1% risk per trade, no compounding — never a percentage of the account as it stands. A configuration that fails on old data is ambiguous: it may be over-fitted, or that market may simply have been a different game, and this test cannot tell those apart. One that works in both structures is not ambiguous. Backtest results; past performance is not indicative of future results.
Price returns to where orders were left behind.
That is the whole idea underneath. A few levels on any chart are the ones large orders were actually filled at, and price keeps coming back to them — first to trade there again, and later, if the level gives way, to collect everybody who defended it.
Most tools delete a broken level. This one turns it around.
Everyone who bought that zone as support is offside the moment it breaks. Their stops sit just beyond it and their exits are orders in the opposite direction, waiting. When price comes back to it from below, it is no longer a floor — it is a queue of people who want out at breakeven.
The engine keeps that level, flips it, and keeps alerting on it. A broken block is removed only once it has genuinely been consumed, rather than the moment price closes through it — which is precisely when it becomes interesting.
Each one measured on its own.
Five lanes. Five measurements.
Every configuration PRO runs was measured on its own — one lane, one timeframe, the same twelve months of gold: Aug 2025 – Aug 2026.
| Lane | Chart | Net | Profit factor | Win rate | Max drawdown | Trades |
|---|---|---|---|---|---|---|
| REGULARS | 5m | +21.5% | 2.24 | 43% | 9.2% | 30 |
| SCALPSHot-regime only — Apr–Aug shown | 5m | +25.1% | 2.76 | 50% | 4.1% | 28 |
| MAGIC | 5m | +43.9% | 1.81 | 46% | 6.9% | 93 |
| REGULARS | 15m | +13.1% | 2.66 | 47% | 2.0% | 15 |
| SCALPS | 15m | +29.7% | 2.22 | 44% | 4.1% | 43 |
One line in that table needs explaining rather than a badge. SCALPS 5m takes trades only in a hot regime, so although it was run across the same twelve months as the rest, it produced trades in a stretch of them — the months shown beside it. It is the same test window, not a shorter one, and the lane sitting out the quiet part of the year is the behaviour it was built for rather than a period chosen after the fact.
Each lane measured independently — fixed position sizing, $100,000 account, 1% risk per trade, no compounding. Figures are per-lane; they are not cumulative across lanes. XAUUSD (Gold Spot), Aug 2025 – Aug 2026. Backtest results — past performance is not indicative of future results.
Worth saying plainly: that year was a strong uptrend in gold. These lanes read structure rather than predict it, but a year that trends less will not hand back numbers like these, and nobody should buy expecting it to. Read the trade counts too — the smallest lane here closed 15 trades, which is a sample, not a track record.
We measured them outside the year we tuned them.
A backtest of the same months a configuration was built on will almost always look good. The only figure worth anything is what those exact settings did on data no tuning decision ever touched — so that is published here too, wins and losses together.
Those five lanes were tuned on the same twelve months they are measured over. That is normal practice, and it is also the reason such tables tend to look good. So in August 2026 we ran them again on the years before that window — data no tuning decision ever touched. 1 of 5 held.
+47,090 · PF 1.371 · 183 trades · max drawdown 13,903 — positive in both halves of that span, and stronger in the later one (PF 1.154, then 1.543) rather than fading.
The other lanes did not reproduce, and we are not going to dress that up. What it means is genuinely open: they may be over-fitted to the recent year, or the market of 2022–2024 may simply have been a different game — this test cannot tell those two apart. It is also why the lane that passed counts for more than five lanes measured only on their own year: a configuration that fails on old data is ambiguous, while one that works in both structures is not. Still a backtest, still one instrument, still not a promise about next year.
The same test was run on the crypto sleeves, and found one more that held:ETH 15m Scalps, +62,229 at PF 1.285 over Oct 2020 – Jul 2025, positive in both halves of that span. Two of the eleven configurations tested reproduced outside their own window; the other nine did not.
ENTRY and PRO
| Capability | ENTRY | PRO |
|---|---|---|
| Every indicator in the catalogue | — | ● |
| The strategy editions — equity curve and trade list in TradingView's Strategy Tester | — | ● |
| One PRO vehicle, your pick — GOLD, INDEX or CRYPTO | ● | — |
| ZONE DIGGA — psychological zones and support/resistance levels, multi-timeframe, on any chart, any market | ● | ● |
| REGIME DIGGA — what kind of market you are in, and how much to believe it | ● | ● |
| Independent sleeves, each with its own alerts | ● | ● |
| Trade levels on every setup — entry, stop, target, position size | ● | ● |
| Contract value detected automatically | ● | ● |
What changed, version by version.
The three most recent of 11 notes for GOLD DIGGA PRO, as posted to subscribers. Open one to read it in full.
GOLD DIGGA PRO ver2.0: major update
GOLD DIGGA PRO ver2.0: major update
Two measured sleeves for gold. A diamond appears only where a sleeve places an order.
Scalps · 15m gold (spot XAUUSD, and now MGC / GC futures): 2022 to May 2025, on data it was not tuned on. 167 trades · +42.8R · PF 1.374, halves PF 1.232 / 1.519. Max drawdown 13.0R. Costs 0.005%/side + 5 ticks (assumed). Longer record ($0.30/oz), spot: 2010–17 PF 1.20, 2018–22 PF 0.99 (flat). MGC: 2011–17 0.96, 2018–22 1.21, 2023–26 1.29. Expect long flat stretches. Correction: our 183 trades / +$47,090 used a chart-TF trend. As shipped, it is the 167 above.
Regular · the overnight breakout (new): one trade a day, fixed-risk stop, held into the afternoon, no target. The same idea is also on TradingView: GOLD BREAKOUT 15M STRATEGY by WillyAlgoTrader. Measured on gold 15m; failed on 24 other symbols. 2010–2026: 4,264 trades, PF 1.14, max DD 23.7R. Before 2010 it lost. A trend-year sleeve: it earns when gold trends. Next to Scalps, 2010–21: +54R → +134R, drawdown 35R → 27R.
A diamond = an order (Scalps):
- one trade at a time;
- limits live 51 bars;
- 50-bar wait after a target. Fill ▲ · target 🏁 · stop ✕ · expired ○. Regular: diamond on the fill bar + an ARMED label.
Also new:
- Fixed: the 15m impulse filter used the 5m threshold.
- One TP for Scalps.
- ⚠️ BAD RUN: a warning when the last 20 Scalps trades fall below −4.58R. Signals are never muted.
✨ Magic watch: a gold diamond where price tags an untested daily high/low. A level, not a signal.
Every symbol: both sleeves run on any 15m chart; off gold a red box says unmeasured (toggle in settings).
Removed: the 5m lanes, old Regulars and Magic trades, Micro Gold, the paste field.
After updating:
- 15m XAUUSD or MGC / GC chart; sleeve table is off by default (Show sleeve table);
- 🕓 Session timezone = Europe/Athens;
- Psych Zone filter = Yes;
- delete and recreate your alerts (Any alert() function call).
GOLD DIGGA PRO ver1.9.1 — three fixes, one clock
GOLD DIGGA PRO ver1.9.1 — three fixes, one clock
A maintenance release. No lane, preset or signal changes.
The session clock follows daylight saving. The counter-trend window was read in “UTC+3”, a fixed offset — Athens in summer, an hour off all winter. The default is now Europe/Athens (UTC+3 summer, UTC+2 winter, switched by the calendar). City zones joined the list; UTC±N stays for a clock that never moves.
“Enable trade manager” is only a display switch now. With it off, two things changed that never should have: a limit diamond jumped from its confirmation candle back to the order-block bar, and the whole trade computation was skipped — too-far-stop signals were drawn instead of skipped, FILLED/EXPIRED alerts never fired, stored trade data was never reset. The trade is always computed now; the switch hides the tooltip and the card, nothing else.
Measured. Gold 15m scalp preset on the bench: identical to the cent in both test windows. 5m diamond count: 122/122 against ver1.9.
Examined and left alone. On a 15m chart the 5m engine reads the last 5m bar of each 15m candle, not all three. A version reading all three was built and measured: the gold 15m preset went from −0.4k / +11.8k to −12.1k / −3.9k. The presets were tuned on the current behaviour — it is part of what they are, so it stays.
After updating: if 🕓 Session timezone shows “UTC+3”, switch it once to Europe/Athens (or your city). Recreate your alerts — an old alert keeps running ver1.9.
GOLD DIGGA PRO ver1.9 — the alert instance and the chart now see the same bars
GOLD DIGGA PRO ver1.9 — the alert instance and the chart now see the same bars
From one alert: a BUY on 18 September at 10:20 whose diamond never appeared. Not delayed — never.
The alert server and your chart were fed different bars. Every higher-timeframe read — the 15m order-block engine on a 5m chart, the regime trend, the 30m / 4H / daily slopes — returned the last closed bar on history but the open bar in realtime, tick by tick. The 15m engine runs on every 5m close, so in realtime it saw a half-formed 15m bar three times per period, and a block it found mid-bar went into its library for good. The alert instance runs realtime from the day you made the alert; the chart rebuilds from history on every load. Three days later they held different libraries — the 10:20 alert asked for 77,639, and the chart’s block at that price was born 55 minutes later with a different shape.
Fixed without touching history. Each read now keeps a value only once its bar has closed; until then it uses the previous bar — which is what history shows there. History is byte-identical to ver1.8: N/N diamond count on the same chart, readable as diamonds drawn in the Data Window. In realtime the alert instance now sees what the chart sees.
New — FILLED and EXPIRED alerts. A resting limit reports FILLED BUY limit Scalp @ … at the touch and EXPIRED … when its pending life runs out (cancel the manual order); a market entry reports FILLED on the diamond’s bar. Per-lane toggles apply.
Retired — the three per-lane alert conditions (Scalp / Regular / Magic). One alert per chart, “Any alert() function call”, carries signals, plans and fills.
No signal, lane or measured configuration changes. Delete and recreate your alerts as “Any alert() function call” — an old alert keeps running the ver1.8 snapshot, with the divergence.