CRYPTO DIGGA PRO

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

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.

CRYPTO DIGGA ver1.0 — the same engine, measured on crypto

GOLD DIGGA PRO’s engine with the metals machinery removed and one rule made absolute: nothing runs that was not measured on this symbol and timeframe.

Twelve cells were measured — BTC and ETH × Scalps/Regulars/Magic × 5m/15m. Four shipped. The other eight do not run, and the status table or a chart notice tells you which and why. There is no fallback configuration and no borrowed numbers: an empty lane is an off lane.

What ships, each with the year measured at adoption:

BTC  5m Scalps v2   +40,580 · PF 1.47 · DD 13.8k · 128 trades
BTC 15m Scalps v1   +21,072 · PF 1.38 · DD  8.3k ·  81 trades
BTC 15m Magic  v1   +17,089 · PF 1.48 · DD  6.3k ·  49 trades
ETH 15m Scalps v1   +41,321 · PF 1.96 · DD  6.4k ·  71 trades
ETH  5m Scalps      hot-only, behind a toggle

The Regulars lane is not in this vehicle at all. All four of its cells were refuted — ceilinged at 16 to 48 trades a year, under the floor where tuning cannot tell better from lucky. Carrying a lane nothing could fill was pure weight, so it is gone, and a pasted lane=reg string is rejected by name.

Two findings worth the read on their own. The ATR max-SL cap that was toxic on BTC 5m is load-bearing on BTC 15m — same lane, opposite answer. And ETH 15m Scalps, the best number of the campaign, took zero adoptions: the metals-measured engine landed on ETH already at its optimum.

Forward validation of all four is in progress. Every number above is a backtest measurement until the forward period confirms it.

#manual ch. 12.

Added before release — 2026-08-30

🌊 FLOW confluence on the card. Four optional sources from FLOW DIGGA ver1.5+. The card says a defended level broke, how long ago and which way; the diamond grows when a level was still standing as the block formed; the tooltip names the nearest standing level each side of the entry in R. None of it filters — the strict doctrine forbids an unmeasured gate as firmly for FLOW as for a lane. Both break directions are drawn, because on 937 trades neither half was the good one.

The untested-daily proximity guard, which no vehicle ever had. PRO ULTRA refuses entries heading into a nearby untested daily level; CRYPTO never carried that rule. On crypto its absence was nearly harmless and that is measured, not assumed: the $15 the sleeves inherited is 0.019% of BTC near 78,000, and running with the guard fully off returned +61,121.02 / PF 1.571 / 138 trades — identical to the cent. It had never once fired. Switched off in the sleeves on 2026-08-31: the 0.25% floor moved BTC to ~$195, which cost two trades a year and stopped the vehicle reproducing its own published rows. Off, it reproduces them exactly.

So the vehicle floors it at 0.25% of price. That number is measured: 15 → +61,121 · 200 → +64,388 · 500 → +19,446 · 1000 → +5,326. Between 15 and 200 is noise; past 500 the lane collapses. 0.25% puts BTC near $195, inside the noise band — gold’s own 0.63% ratio would put it at $470, over the cliff.

One divergence, stated rather than buried: the bench measured BTC at $15, the vehicle runs it near $195. That is two trades a year — 138 against 136, measured. ETH is untouched, its $15 being already 0.60% of price. Everywhere else, what fired in the measurement is what fires on your chart; this is the exception, and it exists because a rail pinned to a dead number is worse than one that moves.

✨ BTC 5m Magic — new sleeve, behind a toggle, default OFF. Both Magic timeframes fade the same daily highs and lows, so the 5m cell was measured and refused on trade count (39-44/yr). It ships now because it was run on data it had never seen and held:

out of sample       +20,545 · PF 1.348 ·  70 trades · DD 16,005
   (Jan 2024 → Jul 2025)
its own year        +10,417 · PF 1.317 ·  40 trades · DD  8,502
the wider window     +6,212 · PF 1.167 ·  44 trades · DD 10,985
   (Jul 2025 → Aug 2026, the span every other sleeve is measured over)

The only lane here whose edge reproduced outside its own year. Off by default because it earns roughly what it draws down, and because that third row is the honest one: stretch its year four weeks earlier and it nearly halves. All three ride on the toggle’s tooltip and on the ledger.

The card was trimmed to what places the order: entry, stop, liquidation, targets with R in brackets, limit life, size. The trade number, date, source row, bounce origin and BUY/SELL row are gone — the axis says when, and the diamond’s position says the direction.