UMA (Optimistic oracle for arbitrary truth ) versus RedStone (Modular oracle that ships new LST, LRT and RWA feeds faster than anyone) — how they differ on type, coverage and what they’re built for.
| UMA | RedStone | |
|---|---|---|
| Type | Optimistic | Push + Pull |
| Update model | Assert-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. | Pull-first modular design: data is signed off-chain and delivered on-demand, or pushed on a schedule — pick per use case. |
| Chains | Ethereum + L2s | 100+ |
| Feeds | Arbitrary data | 1,000+ |
| Security | Economic security via bonding, a dispute window and UMA-holder voting. | Signed data packages verified on-chain; modular delivery across EVM and cross-chain. |
| TVS* | Event-driven | ~$3.6B |
| Token | UMA | RED |
| Best at | Subjective / arbitrary data: prediction-market resolution, insurance, custom claims a price feed can’t express | Yield-bearing collateral — the go-to oracle for liquid staking (LST) and liquid restaking (LRT) tokens |
* Approximate total value secured — dated market snapshot (DefiLlama / provider reports, 2026).
Pick UMA when subjective / arbitrary data: prediction-market resolution, insurance, custom claims a price feed can’t express matters most; pick RedStone when yield-bearing collateral matters more.