CRYPTO DIGGA PRO
The same engine, measured on crypto — BTC and ETH built in, nothing running that was not tested.
CRYPTO DIGGA PRO with ZONE DIGGA and REGIME DIGGA beside it: €20/mo, or €168/yr billed annually. 10-day free trial.
The crypto sibling of GOLD DIGGA PRO — same engine, same paste system, same doctrine, with the metals machinery removed and the crypto campaign’s measurements compiled in.
It is not one strategy with settings. It is a set of finished measurements: each lane runs the exact configuration it was tuned and backtested with, on its own symbol and its own timeframe, including its own regime brain. Nothing to configure below the surface, and nothing firing on a cell nobody measured.
What you get
- BTC and ETH built in, each sleeve running the configuration measured on it
- Every lane carries its own brain — trend timeframe, ADX gate, session filter, cooldowns
- Nothing runs that was not measured; an unmeasured cell stays quiet rather than guessing
- Trade levels on every setup — entry, stop, two targets and a lot size for your account
- Alerts carrying the trade itself — size, entry and stop arrive in the message, not just a ticker
- Any other symbol pastes in as a preset string, read back in full before it runs
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. 2 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 |
| ETH Scalps v1 15m Oct 2020 – Jul 2025 | +41,300 | 1.96 | +62,229 | 1.285 | 310 | held |
| BTC Magic 5m Jan 2024 – Jul 2025 | +6,212 | 1.17 | +20,545 | 1.348 | 70 | held |
| ETH Scalps age75 5m Oct 2020 – Jul 2025 | 0 | 1.40 | −4,376 | 0.993 | 869 | flat |
| BTC Magic v1 15m Mar 2020 – Jul 2025 | +17,100 | 1.48 | −12,899 | 0.939 | 260 | flat |
| BTC Scalps v1 15m Mar 2020 – Jul 2025 | +21,100 | 1.38 | −13,099 | 0.953 | 362 | flat |
| ETH Magic 5m Mar 2021 – Jul 2025 | +15,223 | 1.43 | −37,759 | 0.811 | 223 | lost |
| BTC Scalps v2 5m Mar 2020 – Jul 2025 | +40,600 | 1.47 | −99,482 | 0.828 | 733 | 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.
What changed, version by version.
The three most recent of 4 notes for CRYPTO DIGGA PRO, as posted to subscribers. Open one to read it in full.
CRYPTO DIGGA ver1.2.1 — three fixes, one clock
CRYPTO DIGGA ver1.2.1 — three fixes, one clock
A maintenance release. No sleeve, preset or signal changes.
The session clock follows daylight saving. The counter-trend window was read in “UTC+3”, a fixed offset — an hour off all winter. Default is now Europe/Athens (UTC+3 summer, UTC+2 winter). City zones joined the list; UTC±N stays for a fixed clock.
“Enable trade manager” is only a display switch now. With it off, a limit diamond jumped back to the order-block bar, too-far-stop signals were drawn instead of skipped, FILLED/EXPIRED alerts never fired and stored trade data was never reset. The trade is always computed now; the switch hides the tooltip and the card.
Measured on the bench, 15m scalps, two disjoint windows:
BTC −7.4k / +32.9k → −5.4k / +32.9k
ETH +18.1k / +44.9k → +20.1k / +45.9k
Nothing worse beyond noise.
Examined and left alone. On 15m the 5m engine reads the last 5m bar of each candle, not all three. Reading all three was built and measured — BTC flipped negative in its second window, ETH lost 37k. The sleeves were tuned on the current behaviour, so it stays.
After updating: if 🕓 Session timezone shows “UTC+3”, switch it once to Europe/Athens. Recreate your alerts — an old alert keeps running ver1.2.
CRYPTO DIGGA ver1.2 — the alert instance and the chart now see the same bars
CRYPTO DIGGA ver1.2 — 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.1: 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 two per-lane alert conditions (Scalp / 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.1 snapshot, with the divergence.
CRYPTO DIGGA ver1.1 — the alert and the diamond now agree
CRYPTO DIGGA ver1.1 — the alert and the diamond now agree
The same three fixes as GOLD DIGGA PRO ver1.8, from one report: an alert arrives, there is no diamond on the chart, and hiding the indicator and showing it again brings it back.
The order-block tooltip was evicting your diamonds. Pine allows a script 500 drawing labels and that ceiling cannot be raised. Every block carried one, so on a 5m chart the block library alone held 400 of the 500 — and past the ceiling the oldest go.
It had not earned the room. That label drew nothing; it only answered a hover. And its tooltip was written once when the block was born and never updated, so “Age: 0 bars” said zero on every block, forever, and “Distance” was frozen at that first bar. The rest is on the chart already: the box is the range, its colour is the timeframe and direction, a faded block failed the filter, an FVG has its own box.
Gone, with 12 colour calls per block per bar that repainted invisible text. 400 labels freed on 5m, 200 on 15m. Same blocks, same signals. The breaker tooltip shared that label and goes too.
The alert was firing for trades the indicator had already refused. A signal whose stop is wider than its lane’s maximum is skipped and draws no marker — but the alert fired ahead of that filter. Both are gated on the same thing now.
And the alert carries the trade — SIZE, ENTRY, SL and the limit’s life — instead of the symbol and timeframe alone.
Also: levels stop going negative on un-sleeved coins. The stop buffer and max-SL cap are gold’s dollars, inherited with the fork: subtract 17.5 from a sub-dollar coin and the stop goes below zero; on a $150 coin it is a 12% stop. They now carry as a fraction of price. All four shipped cells and the ETH 5m hot sleeve keep a factor of exactly 1 and do not move.
Recreate your alerts after updating. TradingView stores a snapshot of the script from when the alert was made, so old alerts keep running ver1.0.