Insights on Crypto Payments, Infrastructure, and Operations

Oracle Heartbeat

Blockchain Networks & Protocols

Pronunciation: OR-uh-kul HAHRT-beet

Definition

An oracle heartbeat is the maximum scheduled interval between feed updates when the observed value has not crossed its deviation threshold.

Overview

Contents Hide
  1. How it works and why it matters
  2. Technical context
  3. Practical checks
  4. Related concepts
  5. Further reading

How it works and why it matters

A heartbeat is a feed’s periodic refresh trigger when prices have not moved enough to activate a change-based update. Think of it as a scheduled opportunity to publish another observation, not an absolute promise that a block will contain it at an exact second. The interval may differ by feed and chain. Applications need their own maximum-age rule because outages, delayed reporting, and congestion can push publication past the expected heartbeat. Longer heartbeats save transactions but can increase the time stale data remains usable.

Technical context

An oracle heartbeat is a feed configuration that triggers periodic publication even when market movement remains below the normal deviation threshold.

A heartbeat does not guarantee exact delivery at the deadline, because reporter participation, transmission, congestion, or block inclusion may add delay.

Integrators must obtain the heartbeat for the exact feed and network, monitor missed updates, and define fallback behavior.

Practical checks

Monitor both the advertised interval and the timestamp returned by the specific feed. A heartbeat measured from publication and an application limit measured from source observation can produce different results. During a feed stall, preserving the last good quote for display may be acceptable, but executing new trades against it may not be.

Oracle; Block Inclusion; Blockchain Oracle

Further reading

Example

An exchange-rate oracle advertises a 60-minute heartbeat. The feed last updated at 10:00; at 11:12 no new update has arrived because the network is congested. A checkout requiring data younger than 15 minutes must reject that answer rather than assume the heartbeat guarantees freshness.

Comparison

A heartbeat depends on elapsed time. A deviation threshold depends on measured price movement. Both are publication triggers; neither replaces a consumer's explicit stale-data policy.

Key Takeaway

A heartbeat setting is not a freshness guarantee for each individual transaction.

Sources

  1. Ethereum Documentation: Oracles — Ethereum Foundation (2026-07-30)
  2. Chainlink Documentation — Chainlink (2026-07-30)