Encyclopedia DeFi · Entry 160
Oracle heartbeats and deviation thresholds: when prices update
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Deviation | A configured price change can trigger a new update round. | [1] |
| Heartbeat | An elapsed interval can trigger an update even during low volatility. | [1] |
| Consumer check | Chainlink recommends checking updatedAt or the relevant timestamp for freshness. | [1] |
Triggering a round differs from publishing it instantly
Consider an illustrative feed with a 1% deviation trigger and a one-hour heartbeat. A small price change may not trigger an immediate deviation update, while reaching the heartbeat initiates the update process.
Network congestion or operational delays can affect when the result appears on-chain. The example parameters are not asserted for any particular live feed.
Use a threshold suited to the actual application
A lending protocol, a displayed chart and a settlement contract may tolerate different levels of staleness. The consumer must decide when to reject a value, pause or use another defined path.
Check decimals, quote currency and feed identity as well as age. A fresh answer from the wrong asset pair is still the wrong input.
The same asset can have different feed settings
Heartbeat and deviation settings can differ across chains and between underlying and wrapped assets. Documentation or a value copied from another deployment may therefore be inappropriate.
Record the feed address, chain and configuration observation date when auditing an integration. Do not treat a generic product label as a complete oracle specification.
Direct answers
Questions people ask
Does a heartbeat guarantee an update exactly at that second?
No. It is a trigger condition for the update process; publication can be delayed by network and operational conditions. Consumers still need freshness checks.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
A push-based price feed may update when a price deviation threshold is crossed or a heartbeat interval is reached. These triggers do not make the value a continuous live quote or guarantee zero delay. Consumers must check the feed’s units, timestamp and suitability for their application, using the exact chain and feed configuration.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimDeviation: A configured price change can trigger a new update round.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimHeartbeat: An elapsed interval can trigger an update even during low volatility.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimConsumer check: Chainlink recommends checking updatedAt or the relevant timestamp for freshness.
Scope: DeFi · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:18.493Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Using Data FeedsChainlink
Feed update conditions, chain/feed-specific configuration and consumer checks.
Locator: Heartbeat and deviation thresholds; Data quality · Retrieved: 2026-10-02T17:38:46.139ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Oracle heartbeats and deviation thresholds: when prices update.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/oracle-heartbeat-deviation/