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.
this can trick devs so they think the code is updated but its not, and this will lead to same issue
in previous audit.
update code to 1 Hour.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.