One of the main issues with $AAVE V3, that i hope v4 will fix. ( related to CAPO, so @LlamaRisk could already have solved this issue ) Does the protocol enforce maximum staleness thresholds on oracle price data and revert or pause operations when feeds go stale? Disputed answer: no Xerberus v3 Resolution Reasoning: The user emphasizes the availability but omission of the `latestTimestamp()` call in the AaveOracle interface within Aave v3. Given the security concerns related to stale data from oracles and no counter-evidence provided, the absence of use is supported. Without explicit separation or documentation of intentional design choice to omit this function's call, the provided links corroborate the claim that `latestTimestamp()` is not used, validating the user's assertion. The absence of negative reports in security-critical analysis domains suggests this absence is credible and lends to approving the claim. Key Points: -Absence of a function call supports user's claim when considering security implications. -Lack of explicit documentation or justification for omission reinforces the claim. -In domains where vulnerabilities would be publicly discussed, absence of such discussion supports the claim.