BaseGauge sets boostState.minBoost to a non-bps value which in the constructor which makes it greater than the boostState.maxBoost since maxBoost is set properly in BPS format.
Inside the constructor of BaseGauge we set boostState.minBoost to 1e18, which is not in BPS format compared to maxBoost which is 25000 properly to represent 2.5%
When functions are called that require max > min it will underflow and revert like how when we call below:
_applyBoost will always revert because of the following line in BoostCalculator::calculateBoost:
Core gauge functionality is completely broken as boost calculations will always revert
The gauge system wont be able to apply boosts until setBoostParameters is called to change minBoost
Foundry
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.