DeFiHardhatFoundry
250,000 USDC
View results
Submission Details
Severity: medium
Invalid

Oracle still not updated even after beanstalk code update.

Summary

in previous audit Oracle timeout 4 hours is detected but after beanstalk made changes on codes the timeout still 4 hours
but the comments says the opposite it say: timeout for Oracles with a 1 hour heartbeat but the code still 14400 -> 4 hours.

the code still 4 hour Oracle timeout but the in comments it says timeout for Oracles with a 1 hour heartbeat
so the developers are not aware of this and they didn't change the code.

Impact

this can trick devs so they think the code is updated but its not, and this will lead to same issue
in previous audit.

Tools Used

Recommendations

update code to 1 Hour.

Updates

Lead Judging Commences

inallhonesty Lead Judge about 1 year ago
Submission Judgement Published
Invalidated
Reason: Known issue

Support

FAQs

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