Decentralized Oracle Network (DON)
Abbreviation: DON
Pronunciation: dih-SEHN-truh-leyezd OR-uh-kul NET-wurk (DEE-OH-EN)
Also known as: Decentralized Oracle Network, DON
Definition
A Decentralized Oracle Network is a defined group of independent oracle nodes that reaches agreement on data, computation, or cross-chain results. DONs are commonly associated with Chainlink, where different services and feeds can use different node sets, configurations, and on-chain contracts. The word decentralized does not prove that operators, data sources, or hosting are sufficiently independent.
Overview
Meaning and scope
A Decentralized Oracle Network is a defined group of independent oracle nodes that reaches agreement on data, computation, or cross-chain results. DONs are commonly associated with Chainlink, where different services and feeds can use different node sets, configurations, and on-chain contracts. The word decentralized does not prove that operators, data sources, or hosting are sufficiently independent.
Mechanism and operation
A Decentralized Oracle Network coordinates multiple nodes to perform a specific oracle service. Members may observe data, execute workflows, generate randomness, validate API responses, or verify cross-chain messages before producing a threshold-signed or aggregated report. Integrators should identify the exact DON, signer threshold, report format, update policy, contract address, and supported network. Decentralized Oracle Network (DON) should specify the reported value or event, authorized sources, aggregation method, update trigger, timestamp, decimals, and validity conditions. Multiple reporters do not create independence when they rely on the same exchange, API, infrastructure provider, or market methodology.
Practical payment example
A lending contract requests a price from a network of oracle nodes and rejects an update that fails its freshness or aggregation rules.
Operational checks
The assurance model includes data providers, node operators, signers, transmitters, contracts, governance, and any emergency controls. Applications should enforce freshness and deviation limits, validate the expected feed or contract, and define fallback behavior for missing, disputed, or implausible data. High-value actions may require delayed execution, secondary evidence, or a circuit breaker rather than automatic acceptance.
Distinctions and limits
Security analysis must cover the complete node and data-source composition rather than the brand name alone. On-chain authenticity does not guarantee freshness, correct units, or fitness for a particular business action. Operational takeaway: A DON produces quorum-backed oracle results, but each network’s membership, threshold, sources, contracts, and update policy require verification.
Related reading
Related definitions: Decentralized Oracle, oracle.
Example
A lending contract requests a price from a network of oracle nodes and rejects an update that fails its freshness or aggregation rules.
Comparison
DONs are commonly associated with Chainlink, where different services and feeds can use different node sets, configurations, and on-chain contracts. The word decentralized does not prove that operators, data sources, or hosting are sufficiently independent.
Key Takeaway
A DON produces quorum-backed oracle results, but each network's membership, threshold, sources, contracts, and update policy require verification.
Sources
- Ethereum Documentation: Oracles — Ethereum Foundation (2026-07-30)
- Chainlink Documentation — Chainlink (2026-07-30)