Oracle Providers
Oracle provider taxonomy, freshness monitoring, and how oracle metadata is surfaced in v2 scoring context.
Oracle provider metadata is used for monitoring, market explainability, and alerting. The current asset vector does not apply a blanket oracle-quality cap to every vault score.
Provider Taxonomy
| Provider | Score | Tier | Description |
|---|---|---|---|
| Chainlink | 10 | Prime | Industry standard oracle network |
| Chronicle | 9 | Prime | MakerDAO oracle infrastructure |
| Lido | 8 | Prime | Lido exchange rate feeds, protocol-native |
| API3 | 8 | Prime | First-party oracle network, audited, trusted by Morpho curators |
| Pyth | 7 | Core | High-frequency oracle network |
| RedStone | 7 | Core | Modular oracle provider |
| Exchange Rate | 7 | Core | On-chain protocol exchange rate |
| Custom | 3 | Edge | Custom oracle implementation, unvetted |
| Unknown | 2 | Edge | Unknown oracle provider |
How It Applies
Oracle classification is surfaced on market and oracle metadata, including Morpho market detail. It helps users understand price-source quality and monitor stale or unusual feeds.
For live scoring, asset quality comes from category dimensions, caps, overlays, staleness, and portfolio adjustments. Oracle metadata can still trigger events, alerts, and diligence review, but it is not a universal per-position score ceiling in the current composite path.
Vendor Name Mappings
Oracle vendors are detected from on-chain data and mapped to providers.
| Detected Vendor | Mapped Provider |
|---|---|
| chainlink | Chainlink |
| chronicle, maker | Chronicle |
| pyth, pyth network | Pyth |
| redstone | RedStone |
| api3 | API3 |
| lido | Lido |
| origami, mev-capital, compound, etherfi, renzo, kelp, swell, eigenlayer, pendle | Exchange Rate |
Oracle Freshness
A dedicated worker polls Chainlink, Binance, Pyth Hermes, and configured exchange-rate sources every 15 seconds. Monitor freshness via the Oracle Freshness API.