This is due to the hardcoded value in the BoostController::updateUserBoost function
The problem of the fuction can be seen in the highlighted line of code:
This practically means that when the function is called, it will negatively impact the boost allocation of the user and he won't be able to fix it
The boost allocation of the user will practically be forever messed until pool address call the removeBoostDelegation function. This can be performed for every existing allocation possible, making the BoostController practically useless
Manual review
Restrict the function so that only the user is the msg.sender and allow him to specify the exact amount he wants to change his delegation with, by capping it with his veRAAC token balance
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.