Oracle staleness check present
QuickSwap's assessment for RD-F-059 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Not applicable — no external oracle is consumed, so no updatedAt staleness check is needed. AMM price is always current (derived from pool state at transaction time).
Sources #
- InternalQuickSwap protocol profile §700-profile.md §7: V2 is constant-product AMM (price from reserves); V3/Algebra is tick-based CL — both derive price from on-chain state at time of swap, not from an external feed that could become staleretrieved 2026-05-16
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 quickswap factor RD-F-059 score green collected_at 2026-05-16 08:48:31