When a user wishes to delegate their boost to another user, their corresponding userBoosts mapping is updated. The issue is the delegation functions update the pool address in the mapping to the user they are delegating to so the corresponding pool they are receiving a boost for will be lost.
A user chooses to delegate their boost to another user and calls delegateBoost. The delegation storage variable is initialized with the msg.sender and to parameter. The problem is this to parameter that is supposed to represent who the user is delegating to actually is in the spot in the mapping where the pool address should be.
If we look at how the userBoosts variable is declared, we can see the intended behavior.
Unable to delegate boost to a user for a given pool
Manual Review
There doesnt need to be a new UserBoost mapping created. There is already a delegatedTo variable as part of the UserBoost object.
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.