Oracle providers used
Concrete's assessment for RD-F-048 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No oracle providers are directly consumed by Concrete's vault contracts (ConcreteStandardVaultImpl, AllocateModule, BaseStrategy). The 19 Chainlink feeds in the data cache belong to external strategy protocols (Aave, Compound, Morpho) consumed by those protocols' own contracts, not by Concrete. Architecture.md confirms totalAssets is a cached state variable updated by strategy yield reporting, not external price feeds. Data cache field oracle: null.
Sources #
- GitHubConcrete Architecture.md — totalAssets caching documentationdoc/Architecture.md — totalAssets caching model: 'totalAssets is in fact a state variable at the vault'retrieved 2026-05-17
- ConcreteStandardVaultImpl.sol — source inspectionsrc/implementation/ConcreteStandardVaultImpl.sol — no oracle import, no Chainlink call foundretrieved 2026-05-17
Methodology #
List all oracle providers used (Chainlink, Pyth, Redstone, Uniswap-TWAP, in-house, etc.) per asset/market pair in the protocol.
See the full factor methodology and distribution across all protocols →