_boostState
is incorrectly updated when create/update a lock.
When user creates a lock position, a lock is created and _boostState
, and veRAAC tokens are minted to the user.
In _updateBoostState()
, _boostState
is updated.
veRAACToken::_updateBoostState()
As can be seen, _boostState.votingPower
and _boostState.totalVotingPower
are the values before veRAAC tokens are minted, but _boostState.totalWeight
is already updated in createLock()
. This brings inconsistent values being updated in _boostState
, as only _boostState.totalWeight
is updated to the newest value after user creates a lock.
_boostState
is incorrectly updated. The impact is low though as _boostState
as the updated values are only required by getBoostState()
.
Manual Review
_updateBoostState()
should be called after minting.
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.