No check for startedAt = 0, can result in stale prices reported by the chainlink oracle
The protocol attemps to protect itself from stale price feeds from Chainlink using the following the following code
The problem here is that there is no check that startedAt = 0. According to the chainlink docs, if the sequencer is down, both startedAt and answer are equal to 0. However there is only a check that the answer is equal to 0. This means that in the situation that the both startedAt and the answer are equal to 0, the function getPrice should revert, but in this case it will not since block.timestamp - 0 (startedAt), will always be greater that the default grace period time which is 3600. See the except below
The current implementation of the chainlink sequencer checks will not wokr properly causing the function getprice to pass during sitautions where the sequencer is offline, resulting in unexpected results
Manual Review
Add a check to revert if startedAt = 0.
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.