Chainlink aggregator min/max bound misconfig
Usual (USD0 / bUSD0 / USUAL)'s assessment for RD-F-060 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
USYC uses a Hashnote custom aggregator — not a standard Chainlink feed with published minAnswer/maxAnswer. Chainlink USDC/USD and USDT/USD are standard stablecoin feeds with tight bounds. ETH/USD feed (0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419) is in the data cache oracle_feeds but its actual consumption by DaoCollateral is unconfirmed — the profile notes this may be a broad registry query result. Yellow because: USYC custom aggregator bounds are unknown and cannot be verified as non-misconfigured; stablecoin feeds appear standard.
Sources #
- DocsUSD0 ClassicalOracle | Usual Tech Docstech.usual.money ClassicalOracle USD0 docs: USYC uses Hashnote oracle address 0x4c48bcb2160f8e0adbf9d4f3b034f1e36d1f8b3e — custom IAggregator, not Chainlink-published feed with registry-verified boundsretrieved 2026-05-17
- Usual Data Cache oracle_feeds00-data-cache.json oracle_feeds — includes ETH/USD, USDC/USD, USDT/USD but profile §7 warns ETH/USD may not be consumed by DaoCollateralretrieved 2026-05-17
Methodology #
Determine whether the Chainlink aggregator's `minAnswer` and `maxAnswer` circuit-breaker bounds are misconfigured (too wide or too narrow) for the asset class.
See the full factor methodology and distribution across all protocols →