← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · INDICATOR SERIES TIMING

Crypto Indicator Series: Event Time vs Retrieval Time

Each indicator value belongs to a bar's close time. Values computed later from revised or extended data can differ from what was shown live.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

An indicator series should be keyed by the close time of the bar it belongs to and stored with the time it was computed. Values computed live (during the bar) differ from closed values; values recomputed later from more history (recursive indicators) or revised data can differ again. Store bar time, computation time and whether the value was live or closed, so backtests use what was knowable then.

Which times the data carries

TimePresent?Meaning
Bar close timeKeyWhich bar
Computed atYour logLive vs closed
History startYour logRecursive indicators
Data revisionsRareRecompute flag

See Crypto Indicator Series on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

What to record yourself

Field to storeWhy
bar close timeKey
computed_atKnowability
live/closed flagSignal validity
history startReproducibility
parametersVersion
Indicator Series: a stored recordIndicator Series: a stored record: bar close time — Key; computed_at — Knowability; live/closed flag — Signal validity; history start — Reproducibility; parameters — Version.bar close timeKeycomputed_atKnowabilitylive/closed flagSignal validityhistory startReproducibilityparametersVersion
Every indicator series row carries its own clock. Original ChartsPod editorial graphic.

Example

Indicator Series: event vs retrieval (illustrative)Indicator Series: event vs retrieval (illustrative): 13:00: 1H bar opens; 13:40: RSI computed live: 29; 14:00: Closed: 33; STORE: Both, flagged.13:001H bar opens13:40RSI computed live: 2914:00Closed: 33STOREBoth, flagged
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: an alert log stored live RSI 29 for the 13:00 bar; a backtest using closed RSI 33 never 'saw' that alert. Storing both explains the mismatch.

Related: Crypto Indicator Series: Null vs Zero - Handle Missing Fields Correctly, RSI in Crypto: Warm-Up Bars and Short-History Errors.

Store bar time, computation time and whether the value was live or closed, so backtests use what was knowable then.

Test Crypto Indicator Series on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Questions readers ask

Which time does an indicator value belong to?

Its bar's close time.

Why store computation time?

To separate live from closed values.

Do recursive indicators change with history?

Yes; record the start.

Sources and methodology

Field definitions come from DEX Screener's API reference and CoinGecko's onchain API documentation, read 17 October 2026. Where a schema doesn't document a timestamp, this guide says so and recommends recording retrieval time yourself.

  1. TradingView Pine Script: Repainting — live vs historical calculation.
  2. ChartsPod indicator reference — indicator calculations.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.