Oracle role per asset

Dolomite's assessment for RD-F-049 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Each asset has exactly one oracle entry in ChainlinkPriceOracleV1 tokenToAggregatorMap — no secondary or fallback oracle per asset. Chainlink feeds = Primary for ETH/BTC/USDC/USDT/LINK/WBTC/COMP/UNI. Chronicle = Primary for some Berachain assets. Redstone = Primary for select Berachain/Ethereum assets. Pendle TWAP = Primary for PT component of PT-token pricing. Yellow because single-oracle-per-asset design (no fallback role assigned).

Sources #

GitHub
ChainlinkPriceOracleV1.soldolomite-exchange/dolomite-margin/blob/master/contracts/external/oracles/ChainlinkPriceOracleV1.sol — tokenToAggregatorMap is a single mapping per token; no fallback structureretrieved 2026-05-16
Docs
Pendle PT Integration — Dolomitedocs.dolomite.io/integrations/pendle/pendle-pt — PT to base uses Pendle TWAP; base to USD uses Chainlink/Chronicleretrieved 2026-05-16

Methodology #

For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol dolomite factor RD-F-049 score yellow collected_at 2026-05-16 11:12:56