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 |
Solana Oracle Attribution
Solana (Kamino) reserves resolve their price sources from on-chain reserve configuration, and most route through Scope, Kamino's on-chain price aggregator, whose chains compose primary sources (Chainlink on Solana, Pyth), TWAPs, and capped/floored derivations. Attribution walks the full Scope chain recursively:
- A reserve whose configuration resolves to a single concrete source is attributed to that provider exactly.
- A reserve composing multiple sources is attributed conservatively to the worst-scoring source in the chain (the platform reads the freshest at runtime; scoring assumes the weakest link).
- Scope- and Switchboard-attributed feeds score 6 on the provider quality ladder.
- An unresolvable attribution is scored Unknown (2) — stated, never silently absent.
Freshness for monitored Solana feeds is polled from the same Scope accounts the protocol itself reads, on a 60-second cadence, with staleness thresholds set equal to the protocol's own on-chain maximum price age — an alert fires at the same threshold the protocol enforces, within one polling interval of detection latency.
Oracle Freshness
A dedicated worker polls the monitored feeds — Chainlink, Chronicle, API3, RedStone, and Pyth families on EVM chains every 15 seconds, Solana Scope accounts on a 60-second cadence — with independent comparison baselines used for deviation checks. Monitor freshness via the Oracle Freshness API.