Incosistent calculation of voting power
Summary
The code seems to be in transition from using the voting state lib, where the power linearly decreases over time, to use the time weighted logic instead. Currently the voting power is assumed to be the balance of veToken, however the function veRAACToken::getVotingPower is still using the voting state lib, this can have implications such as not reaching consensus for valid proposals due to a decreasing individual power while the total supply does not follow this trend.
Vulnerability Details
Impact
Tools Used
Manual review.
Recommendations
Use a consistent logic accros the codebase, in the current state it seems to be using the veToken balance as the power.
Prize pool breakdown
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.