Oracle staleness check present
Aerodrome Finance's assessment for RD-F-059 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Not applicable — no external oracle consumed, so no oracle staleness check is needed. Pool reserves update on every swap transaction; there is no timestamped oracle value to check for staleness.
Sources #
- GitHubAerodrome Pool.sol — live reserve state, no oracle staleness conceptPool.sol getReserves() — returns live reserve0, reserve1, blockTimestampLast (internal state, not oracle timestamp)retrieved 2026-05-04
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 →
rubric_version v1.7.0 protocol aerodrome factor RD-F-059 score not_applicable collected_at 2026-05-04 19:56:03