Fast answer
Pine Script crypto-signal checks prove whether the script logic, alert timing, settings, and final result were reviewable.
Before accepting a Pine Script signal, record script version, indicator or strategy type, inputs, timeframe, repainting notes, alert function behavior, payload, delivery route, updates, and final close record.
If a provider hides the script version or settings used for a signal, the result cannot be replayed or audited cleanly.
Script checks
What to inspect in Pine Script crypto signal records.
Script version
The code version and release date should match the alert and final result.
Inputs
Settings, timeframe, symbol source, and chart type should remain visible.
Alert behavior
The record should show alert calls, frequency, strategy events, or webhook message fields.
Repaint risk
Repainting, lookahead, MTF requests, and bar-close rules should be documented.
Source context
Script-based signals need code version, inputs, timeframe, alert function behavior, webhook payload, and outcome records.
TradingView's Pine Script alert documentation explains alert calls, alert conditions, and strategy alert behavior. CSR treats script-based signals as reviewable only when code context and live alert records connect to final outcomes.
Review standard
A reviewable Pine Script signal ties code context to live alert evidence.
For CSR evidence review, Pine Script records should include code version, script type, inputs, timeframe, repainting notes, alert frequency, payload, delivery route, updates, and final outcome.