QuantAMM
QuantAMM
49,600 OP
View results
Previous Next
Submission Details
Severity: low
Invalid

off-by-one error in oracle staleness check

huntoor

Summary

Oracle staleness check uses (>) instead of (>=), causing valid oracle data to be incorrectly marked as stale.

Vulnerability Details

In UpdateWeightRunner::_getData(), the oracle staleness check uses:

if (oracleResult.timestamp > block.timestamp - oracleStalenessThreshold)

When timestamp exactly equals the staleness threshold, valid data is incorrectly rejected.

Impact

  • Valid oracle updates will fail unnecessarily

  • Pool weight updates may revert when they should succeed

Tools Used

Manual review

Recommendations

Change the comparison operator from > to >= to include the boundary case:

if (oracleResult.timestamp >= block.timestamp - oracleStalenessThreshold)
Updates

Lead Judging Commences

n0kto Lead Judge 10 months ago
Submission Judgement Published
Invalidated
Reason: Non-acceptable severity

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.

Give us feedback!