How Does an Oracle Network Handle Conflicting Data Submissions from Different Nodes?

Oracle networks handle conflicting data submissions through a consensus mechanism, most commonly by calculating the median of all submitted data points. The median price is used because it is statistically robust, meaning a small number of malicious or outlier submissions will not significantly skew the final aggregated price.

Nodes that submit data far from the median are typically flagged and may face slashing.

How Do Aggregators Handle Data from Exchanges That Are Offline or Reporting Outlier Prices?
How Many Malicious Nodes Are Required to Successfully Skew a Median Price in a 13-Node Oracle Network?
What Is a “Median Price” Calculation and How Does It Compare to a Trimmed TWAP?
How Is the “Historical Accuracy” of an Oracle Node Quantitatively Measured and Used for Weighting?
What Advantage Does a Median-Based Price Aggregation Have over a Mean-Based Aggregation?
In a Scenario with an Even Number of Oracle Nodes, How Is the Median Price Calculated?
How Does a Median Price Calculation Compare to TWAP for Settlement Fairness?
What Are the Computational Overheads of Calculating a Median versus a Simple Average On-Chain?

Glossar