Fast answer
Crypto signal multi-timeframe checks prove whether higher-timeframe context was available before the alert.
Before accepting an MTF signal, record chart timeframe, requested timeframe, symbol, source exchange, confirmation rule, lookahead behavior, alert timestamp, delivery record, updates, and final close record.
If the higher-timeframe value was not known when the lower-timeframe alert fired, historical results can look better than live signals.
MTF checks
What to inspect in multi-timeframe signal records.
Chart timeframe
The base timeframe controls alert timing and execution assumptions.
Requested timeframe
Higher-timeframe data should be available at the claimed decision point.
Lookahead setting
The record should show whether future higher-timeframe values could leak into history.
Confirmation timing
The alert should prove when the higher-timeframe value became confirmed.
Source context
Multi-timeframe signal records should show requested timeframe, chart timeframe, data source, lookahead behavior, confirmation rule, and final status.
TradingView's other-timeframes documentation explains that requested data can introduce lookahead concerns, especially with higher-timeframe context. CSR treats MTF context as incomplete unless the provider shows what data was knowable at alert time.
Review standard
A reviewable MTF signal proves the higher-timeframe evidence was not imported from the future.
For CSR evidence review, MTF records should include chart timeframe, requested timeframe, symbol, data source, confirmation rule, lookahead setting, alert time, payload, updates, and final outcome.