ORACLES
ON-CHAIN × OFF-CHAIN DATAAn external source produces a value. An oracle observes it, timestamps its own reception, and evaluates freshness before a protocol would ever act on it. Everything below is real data from that pipeline — not a simulation.
Polling every 45s while this tab is visible. Session history is local to this browser tab, bounded to the last 24 observations — CoinGecko's free endpoint doesn't expose historical data, so this is not the provider's own history.
Requesting the first observation…
Source: CoinGecko's keyless public API, fetched server-side by the Oracle API — this browser never calls CoinGecko directly. “Observed at” is CoinGecko's own timestamp for the value; “received at” is when this client's request reached the Oracle API. Their difference is latency — the real gap between something happening off-chain and a protocol finding out about it. A future phase can add an on-chain observation alongside this one for direct comparison; nothing here assumes there will only ever be one source.