The Incorrect Price Validation for Long Token issue occurs because the long token's price is validated against the index token's price range instead of its own.
In the _validatePrice
function, the long token is checked against the index token's price range. The MarketPrices
struct (from ./libraries/StructData.sol
) has separate fields for each token's price range
The long token should be validated against its own price range (prices.longTokenPrice
), not the index token's
Validation fails unnecessarily because the long token is compared to the index token's range, even though its price is valid
Foundry
Likelihood: None/Very Low, everytime the keeper send a price via run/runNextAction (sent by the Gamma keeper). Impact: Medium/High, does not check the longTokenPrice, it could go out of range. Keep in mind indexToken == longToken, an error from the keeper could be considered informational.
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.