oracles.ink

UMA vs Chronicle

UMA (Optimistic oracle for arbitrary truth ) versus Chronicle (Gas-efficient, fully verifiable oracle born inside MakerDAO ) — how they differ on type, coverage and what they’re built for.

UMAChronicle
TypeOptimisticPush
Update modelAssert-and-dispute: any data is proposed, can be challenged within a window, and is settled by a token-holder vote (the DVM) only if disputed.Scribe: Schnorr signature aggregation decouples validator count from verification cost, so updates stay cheap as the validator set grows.
ChainsEthereum + L2sEthereum + L2s
FeedsArbitrary data160+
SecurityEconomic security via bonding, a dispute window and UMA-holder voting.Transparent validator set with cryptographic (Schnorr) aggregation; every update is independently verifiable.
TVS*Event-driven~$7.5B
TokenUMA
Best atSubjective / arbitrary data: prediction-market resolution, insurance, custom claims a price feed can’t expressLowest gas cost in the market (≈63% cheaper than Chainlink on Ethereum), with a strong RWA / institutional focus

* Approximate total value secured — dated market snapshot (DefiLlama / provider reports, 2026).

UMA

  • Can verify ANY claim, not just prices
  • Cheap when undisputed
  • Ideal for prediction markets & insurance
  • Latency from the dispute window
  • Not suitable for real-time price feeds

Chronicle

  • Cheapest on-chain updates (Schnorr aggregation)
  • Fully transparent and verifiable
  • Institutional pedigree (Maker/Sky)
  • Smaller feed catalogue than Chainlink/Pyth
  • Push-only (no on-demand pull yet)

Bottom line

Pick UMA when subjective / arbitrary data: prediction-market resolution, insurance, custom claims a price feed can’t express matters most; pick Chronicle when lowest gas cost in the market (≈63% cheaper than chainlink on ethereum), with a strong rwa / institutional focus matters more.