Fast answer
Crypto signal repainting checks prove whether an alert could disappear, move, or change after live data updates.
Before accepting a repainting-sensitive signal, record the script version, chart timeframe, trigger rule, whether the bar was confirmed, alert frequency, screenshot timestamp, webhook payload, settings, updates, and final close record.
If a provider shows only historical chart markers without the live alert timestamp and confirmation rule, the signal can look cleaner than it was in real time.
Repaint checks
What to inspect in crypto signal repainting records.
Live-bar behavior
Check whether the signal can appear during an open candle and vanish before the candle closes.
Confirmation rule
The record should show whether the provider waited for a confirmed bar or used intrabar alerts.
Code and settings
Script version, inputs, timeframe, and any repaint-related settings need to stay attached to the result.
Alert proof
A reviewable record connects original alert, delivery log, update trail, and final close.
Source context
TradingView explains that repainting can come from values that fluctuate during realtime bars.
TradingView's Pine Script repainting guide explains ways to avoid repainting, including requiring confirmation on the realtime bar's closing update. CSR treats repainting as a signal-integrity issue that must be disclosed before ranking provider evidence.
Review standard
A reviewable repainting-sensitive signal proves what was known in real time.
For CSR evidence review, repainting-sensitive records should include script version, chart source, timeframe, trigger condition, confirmation status, alert frequency, original timestamp, payload, edits, updates, and final status.