Oracle staleness check present
JustLend DAO's assessment for RD-F-059 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No staleness check is visible in the oracle contracts. SimplePriceOracle.sol stores prices in a mapping(address => uint) without any timestamp or updatedAt field. PriceOracleProxy.sol reads prices without checking Chainlink's updatedAt return value. If the poster goes offline, stale prices persist indefinitely. The protocol documentation makes no mention of staleness validation. Confidence medium because Tronscan direct source read was blocked — GitHub source may not reflect TVM-deployed state exactly.
Sources #
- GitHubJustLend SimplePriceOracle.sol raw sourceSimplePriceOracle.sol source: prices stored in mapping(address => uint) with no timestamp field and no staleness check logicretrieved 2026-05-17
- Price Oracle - JustLend DAO DocumentationJustLend price oracle documentation: no mention of staleness threshold, heartbeat, or stale-price rejectionretrieved 2026-05-17
Methodology #
Determine whether the protocol rejects oracle reads older than a declared maximum age (i.e., checks `updatedAt > block.timestamp - maxStaleness`).
See the full factor methodology and distribution across all protocols →