Oracle price deviation >X% from secondary
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-099 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Oracle price deviation vs secondary source signal (T-09 phase-2 signal tier, tier-B). Applicable with limited actionability due to immutable PriceFeed contracts. Threshold: primary-vs-secondary deviation >1% sustained 4 blocks on a safety-critical feed. Current posture: Chainlink ETH/USD feed 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419 (3600s heartbeat, 0.5% deviation threshold) is active and healthy per cache oracle_feeds. No secondary-source deviation detected via public monitoring. Structural note: v2 PriceFeed contracts are immutable (no admin can replace the Chainlink address), limiting remediation path but not changing the current clean posture. Signal would NOT fire today.
Sources #
- Internal00-data-cache.json oracle_feedsData cache oracle_feeds includes ETH/USD Chainlink feed 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419 with heartbeat_seconds=3600, deviation_threshold_pct=0.5; active and healthyretrieved 2026-05-16
- Liquity v2 mainnet contract addressesv2 PriceFeed contracts for WETH, wstETH, rETH branches; all immutable with no admin-replaceable oracle addressretrieved 2026-05-16
Methodology #
Detect whether the primary oracle's reported price deviates >X% from the best available secondary source (another feed or venue).
See the full factor methodology and distribution across all protocols →