Oracle staleness check present
Jito'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 #
Staleness check present in StakePoolRate.sol: validateBlockTime() called against both allowedUpdateStaleness (for updatePool() calls) and allowedRateStaleness (for getRate() calls). Both are immutable thresholds set at deployment. If stale, getRate() reverts — consuming protocols receive revert rather than stale data.
Sources #
- GitHubStakePoolRate.sol — staleness validationStakePoolRate.sol: validateBlockTime(lastUpdateSolanaBlockTime, allowedRateStaleness >= block.timestamp ? 0 : block.timestamp - allowedRateStaleness)retrieved 2026-04-29
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 jito factor RD-F-059 score green collected_at 2026-04-29 15:50:23