Offchain Reporting (OCR)

Overview

OCR reduces the cost and latency of oracle updates by moving most communication and aggregation away from the blockchain. Nodes observe data independently, exchange signed messages through a peer network, and agree on a report. One node transmits the report on-chain, where a contract verifies signatures from the configured oracle quorum. This avoids separate transactions from every node while preserving accountable multi-node approval. OCR versions support different products and report workflows.

Operators need reliable data sources, networking, keys, timing, and transmitter funding. Applications should verify the feed contract, report freshness, decimals, and update conditions. Quorum agreement protects against a limited number of faulty nodes but does not prove that correlated data sources reflect the true market. This distinction is essential when a technically valid oracle message produces an economically incorrect payment, liquidation, or release decision. Audit records should retain the exact report, block reference, source configuration, and rule that consumed it.

Offchain Reporting (OCR) should specify the reported value or event, authorized sources, aggregation method, update trigger, timestamp, decimals, and validity conditions. On-chain authenticity does not guarantee freshness, correct units, or fitness for a particular business action.

Multiple reporters do not create independence when they rely on the same exchange, API, infrastructure provider, or market methodology. The assurance model includes data providers, node operators, signers, transmitters, contracts, governance, and any emergency controls. Practical implication: OCR aggregates oracle observations before one on-chain submission, reducing cost while preserving quorum-backed report verification. Offchain Reporting is Chainlink’s protocol family for aggregating oracle-node observations off-chain and submitting one quorum-signed report for on-chain verification.