Oracle staleness check present
Meteora'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 #
No push-oracle is consumed; no staleness check is required or present in swap path. DLMM/DAMM/DBC read on-chain pool/bin state which is always current. Not applicable.
Sources #
- DocsMeteora DLMM ConceptsDLMM pricing from bin state: no latestRoundData() or updatedAt staleness check; price is always current from pool stateretrieved 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 meteora factor RD-F-059 score not_applicable collected_at 2026-05-16 10:03:05