Skip to content
Signal Pilot

Non-Repainting Policy

🎯 Why This Matters (For Traders)

Before diving into technical details, here's what non-repainting means in practical terms:

What is Repainting?

Some indicators change their past signals after new bars form. For example, an indicator might show a "buy" signal on an older candle when you look at it today, but that signal wasn't actually there yesterday when you were trading. This is called "repainting" and it creates misleading backtests.

Signal Pilot's Non-Repaint Guarantee

Signal Pilot indicators are audited to ensure that once a signal appears on a closed candle, it stays there permanently. What you see on historical candles is exactly what appeared in real-time. This allows for:

  • Accurate backtesting and performance evaluation
  • Reliable alert configuration
  • Confidence that historical signals represent actual market conditions
  • No false backtesting results

How Can You Verify This?

Common methods users use to verify non-repainting behavior:

  1. Replay mode test: Use TradingView's bar replay feature and compare signals as bars form vs. after they're finished
  2. Screenshot comparison: Take screenshots of signals as they form, then compare to the same candles days later
  3. Alert logs: Compare alert timestamps to when signals actually appear on charts
  4. Code audit: Review the technical implementation (see sections below)

Educational Purpose

The technical sections below provide code-level verification for developers and advanced users. This transparency allows independent verification of non-repainting claims.

Signal Pilot is designed to be deterministic on candle close.

  • Close-confirmed signals — Alerts fire only when barstate.isconfirmed.
  • HTF data — Pulled with request.security(..., lookahead_off) and only accepted after the HTF bar closes.
  • Pivots & divergences — Only drawn after the right-side pivot confirms; then anchored back to the original bar.
  • Anchoring — Labels/markers use x=bar_index and yloc.price to avoid wobble.

What this means: No future-bar lookahead. Backtests and alerts match live behavior.