In this issue warden has noticed, that each time draw is closed, then lastClosedDrawId variable is increased and when user claim prizes, then vault portion is calculated incorrectly and is shifted by 1 draw.
Solution
This issue was fixed by removing +1 shift for the _endDrawId. In the comments developers has discussed, proposed solution by warden and realized, that _startDrawId was calculated correctly. Fix looks good.
Lines of code
Vulnerability details
Issue mitigated
About the problem
In this issue warden has noticed, that each time draw is closed, then
lastClosedDrawId
variable is increased and when user claim prizes, then vault portion is calculated incorrectly and is shifted by 1 draw.Solution
This issue was fixed by removing +1 shift for the
_endDrawId
. In the comments developers has discussed, proposed solution by warden and realized, that_startDrawId
was calculated correctly. Fix looks good.