Oracle staleness check present
M^0'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 timestamped oracle feed used. No updatedAt staleness check is needed or applicable. Rate model is updated on-chain only when TTG governance executes a proposal to change the rate parameter.
Sources #
- GitHubMinterGateway.sol sourcem0-foundation/protocol main/src/MinterGateway.sol and rateModels/ — no timestamped feedsretrieved 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 m0 factor RD-F-059 score not_applicable collected_at 2026-05-16 09:46:19