Different decimals between maxBoost and minBoost parameters will cause all gauge interactions to fail when veRAACToken.totalSupply() > 0 and gaugeWeight > 0, preventing users from interacting with the gauge system.
In BaseGauge.sol, the constructor sets maxBoost to 25000 (2.5x) and minBoost to 1e18, using different decimal scales. This causes underflow in BoostCalculator.sol when calculating boostRange.
This causes underflow in the boost calculation:
The protocol becomes unusable as key functions like state() and withdraw() will revert due to the updateReward modifier's call chain: _updateReward() => earned() => getUserWeight() => _applyBoost() => calculateBoost().
Align the decimal scales between maxBoost and minBoost:
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.