It is expected that multiple vesting schedule will be created for a benificary. This can be seen in the createVestingSchedule function (uint256 newCategoryTotal = categoryUsed[category] + amount;). Further when a new vesting schedule is made for a benificary, the old vestingSchedule.releasedAmount is not updated to 0. This causes amount released less than expected.
The amount of tokens released is calculated as follows:
It can be seen that the vestedAmount is subtracted from the releasedAmount , which if the releasedAmount is not updated during the creation of the vesting schedule, will return less than expected values.
vesting schedule functionality broken
manual review
update the vestingSCedule.releasedAmount = 0 when creating a new vesting schedule.
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.