Submitted by leastwood
TwapOracle.consult() is missing additional validations to ensure that the round is complete and has returned a valid/expected price. The consult() improperly casts an int256 price to uint256 without first checking the value. As a result, the variable may underflow and return an unexpected result, potentially causing further issues in other areas of the protocol that rely on this function.
Additionally, the GasThrottle.validateGas() modifier utilises Chainlinks latestAnswer() function which lacks additional checks for stale data. The latestRoundData() function facilitates additional checks and should be used over latestAnswer().
Manual code review.
Chainlink best practices.
Consider validating the output of latestRoundData() to match the following code snippet:
This needs to be updated in TwapOracle.consult() and in GasThrottle.validateGas(). The latter instance should have the latestAnswer() function replaced with latestRoundData() in order to avoid stale data.
SamSteinGG (Vader) confirmed 
