Skip to main content
Existing oracle alternatives for getting a price quickly are typically m-of-n approaches like Chainlink or Pyth. With respect to m-of-n oracles, the openOracle approach has several key advantages:

​
Security

openOracle does not rely on trusting m-of-n whitelisted and KYC’d participants. The trust model is based on 1-of-n participants in the oracle network acting in their own self-interest. Dishonest participants can lose an uncapped amount of money, and the best of the network accumulate the most resources. With m-of-n oracles, there is no market mechanism to enforce that the cost of corruption is greater than the profit from corruption. Security is also configurable per oracle instance. Users choose how much to pay for how much security by setting initial liquidity, settlement time, and multiplier per price request. A $100 swap and a $10 million perpetual position can use different parameters suited to their risk, rather than relying on a one-size-fits-all oracle feed.

​
Speed

In m-of-n oracles like Pyth and Chainlink, the price is only valid once there are m signers. This means they can only be as fast as the slowest of the m signers. In openOracle, reporting speed is based on the fastest of all n participants, which is a permissionless set. The fastest network participants accumulate the most resources and slow reporters lose money. In m-of-n setups, there are no brutal incentives punishing latency, and there is a fundamental constraint on speed because of the m signers requirement and consensus latency overhead of aggregating the signatures. While the openOracle design includes some request latency via the settlement time, the price at time of settlement is temporally as close as possible to the true price at that time.

​
Accuracy

Oracle accuracy automatically adjusts to market volatility over the settlement time through a competitive market process. The no-dispute band — the range around the true price where a report survives without dispute — scales with σ(T)\sigma(T), the volatility over the settlement time. In calm markets, accuracy is tight. In volatile markets, it widens naturally. No manual tuning, governance votes, or deviation thresholds are required. This is a consequence of the dispute EV framework: honest disputers profit when the price error exceeds ~0.65⋅M⋅σ(T)0.65 \cdot M \cdot \sigma(T), so the equilibrium no-dispute band is always proportional to background volatility. See Oracle Accuracy & Cost for the full derivation. In m-of-n oracles, accuracy (for example reported confidence in Pyth) is fundamentally restricted by how much the quoters agree with each other and the latency of aggregating their signatures. In openOracle, accuracy is determined by competitive arbitrage — anyone can tighten the price by disputing. Because the oracle is settled by real token commitments on-chain, it automatically reflects the true price of the spot assets in the local blockchain environment. If an event causes a token to trade at a premium or discount on a specific chain — for example, USDC rising in value on Arbitrum during periods of high demand — the oracle price adjusts accordingly without any external feed needing to update. Prices are always network-local.

​
Execution

The accuracy and locality properties above make openOracle useful as a direct execution path, not just a data feed. Applications can request a price and execute a swap, perp, or other settlement using the oracle price. Because the no-dispute band is tight and volatility-scaled, and the price reflects the local on-chain environment, execution quality inherits both properties — users get pricing that tracks real local market conditions.