Oval

• Name: Oval
• URL: https://uma.xyz/oval
• Category: oracle-delay wrapper / OEV recapture middleware / MEV-share-backed oracle-update auction layer
• Tags: ethereum-ecosystem
• Summary: Oval delays third-party oracle updates and sells the backrun window. That is the product. It is not a new oracle network; it is a control layer over when fresh oracle data becomes usable.
• What it does:
  • Wraps existing oracle feeds behind a Chainlink-compatible interface so a protocol can often integrate by swapping the feed address rather than rewriting core logic
  • Returns stale or gated price data until a permissioned actor calls unlockLatestValue() through the auction flow
  • Lets searchers compete to backrun the newly unlocked update so oracle-triggered liquidation value can be redirected to the protocol
  • Uses a lockWindow fallback so the protocol eventually gets public data even if no updater unlocks promptly
  • Splits the system across source adapters, destination adapters, controllers, and the core Oval contract, which makes the routing and permissions surface explicit
  • Depends on permissioned updaters and operational auction routing rather than fully trustless onchain verification of the kickback path
• Key claims:
  • The official materials define Oval narrowly and correctly: it auctions oracle updates to reclaim OEV rather than trying to pose as a fresh oracle network
  • The contract logic is the real source of truth. unlockLatestValue() is expected to be sent privately, and internalLatestData() intentionally serves stale values until an allowed release point
  • The OpenZeppelin audit surfaces the main trust assumption plainly: Oval relies on trusted updaters because the current MEV-Share path cannot verify kickback parameters onchain
  • The auction path is only half the story. The fallback path matters just as much because it determines how the wrapped protocol degrades when the updater flow fails or stalls
  • The useful comparison is with api3-oev: Api3 routes first-party oracle update rights through oracle-owned infrastructure, while Oval wraps somebody else’s feed and adds a permissioned unlock-and-auction layer above it
• Whitepaper: No canonical standalone Oval whitepaper surfaced in this pass. The strongest primary materials were the official launch post, the contracts repository, the core Solidity files, and the OpenZeppelin audit collected in ../whitepapers/oval-primary-sources-2026-05-11.md.
• Sources:
  • https://uma.xyz/oval
  • https://docs.oval.xyz/
  • https://medium.com/uma-project/announcing-oval-earn-protocol-revenue-by-capturing-oracle-mev-877192c51fe2
  • https://github.com/UMAprotocol/oval-contracts
  • https://raw.githubusercontent.com/UMAprotocol/oval-contracts/master/README.md
  • https://raw.githubusercontent.com/UMAprotocol/oval-contracts/master/src/Oval.sol
  • https://raw.githubusercontent.com/UMAprotocol/oval-contracts/master/src/DiamondRootOval.sol
  • https://www.openzeppelin.com/news/uma-oval-audit

Internal linkages

• Closest OEV analogue: api3-oev.
• Feed surface being wrapped and monetized: chainlink.
• Orderflow and auction control-plane anchor: flashbots-auction.

Control surface

• Oval decides when fresh data is released, who gets to unlock it, and how the auction path degrades when it fails.

• That makes the updater set, private-routing path, and fallback timing more important than any generic oracle label.

• Keep the comparison budget short. The note does not need to spend scarce link space on the broader UMA stack unless the dispute machinery is the actual question.

• Last reviewed: 2026-06-03 UTC