UMA

UMA’s Optimistic Oracle V3 is for an application that needs to resolve a specific claim about offchain reality. Instead of exposing a standing market-data value, it accepts an assertion under stated resolution criteria and gives potential disputers time to challenge it before the result is treated as final.

An assertion settles after its liveness window

An application or user submits a claim and associated parameters, beginning its liveness period. If nobody disputes within that window, a settlement call can make the result available to the consuming contract; the answer is claim-specific and is not a continuously updating value governed by a price-feed heartbeat.

A dispute sends the assertion to UMA’s Data Verification Mechanism. That outcome determines how the proposer and disputer bonds settle before an integrating application should rely on the result, so a system needing immediate action must separately account for delayed-settlement risk.

Bonds create an incentive to inspect a claim

The assertion specifies a bond token, bond amount and liveness window. Both the asserter and a disputer place capital at risk; a higher bond can make a valuable false claim more worthwhile to inspect, but it also ties up more capital for honest participants and can reduce practical challenge participation if set too high.

The assertion’s wording, evidence context and time boundary are security-critical. A vague, subjective or inaccessible claim can be difficult for potential disputers and voters to evaluate even when the smart-contract flow is working as designed.

Disputes use a separate voter resolution process

In the DVM, UMA stakers commit votes and later reveal them; the stated process uses 24-hour commit and reveal periods and requires at least 65% of voted stake for one outcome. Stakers who do not vote or vote against the majority can be slashed, with value redistributed to majority voters.

Chainlink Data Feeds are the contrasting option when a protocol needs an available, pre-published onchain data point. UMA is suited to a contestable, application-defined outcome with bonds and liveness; Chainlink supplies feed-specific aggregation and deviation or heartbeat updates, with the consumer responsible for stale-data controls.