Oracle Median

Overview

An oracle median is an aggregation result obtained by sorting accepted observations and selecting the middle value, or a defined combination of the two middle values. It is commonly used to limit outlier influence. Median aggregation tolerates some extreme submissions without averaging them into the result. However, it does not assess market quality by itself. Correlated publishers, duplicated sources, stale observations, or control of enough positions can still move the median. Implementations must define eligibility, quorum, timestamp windows, duplicate handling, even-number behavior, precision, and scaling. Consumers should inspect publisher concentration and confidence information instead of treating the median as certain truth. During thin or rapidly moving markets, a robust median may still lag the price relevant to the application.

The trust model includes data providers, node operators, signers, transmitters, contracts, governance, and any emergency controls. Multiple reporters do not create independence when they rely on the same exchange, API, infrastructure provider, or market methodology. High-value actions may require delayed execution, secondary evidence, or a circuit breaker rather than automatic acceptance. Integrations should enforce freshness and deviation limits, validate the expected feed or contract, and define fallback behavior for missing, disputed, or implausible data.

Review records should retain the exact report, block reference, source configuration, and rule that consumed it. This distinction is essential when a technically valid oracle message produces an economically incorrect payment, liquidation, or release decision. A report can be validly published on-chain while still being stale, mis-scaled, or unsuitable for the decision that consumes it. Oracle Median should specify the reported value or event, authorized sources, aggregation method, update trigger, timestamp, decimals, and validity conditions.