The GaugePointFacet contract lacks proper handling for edge cases where percentOfDepositedBdv
exactly matches upper or lower thresholds.
##Impact
Unchanged or undefined gauge points may disrupt protocol operations, impacting efficiency and user experience.
If percentOfDepositedBdv
precisely matches the upper or lower threshold, the function may not update the gauge points. This lack of responsiveness can lead to stagnant gauge points, impacting the protocol's efficiency and responsiveness to changes in the percentage of deposited BDV.
In cases where percentOfDepositedBdv
exactly matches the upper or lower threshold, the function may not define the newGaugePoints
variable. This can result in unpredictable behavior, as the gauge points' value remains unclear and may not reflect the intended state of the protocol.
Implement conditions in the defaultGaugePointFunction
to address edge cases, ensuring more reliable gauge point calculations and protocol stability.
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.