Merkle root update could potentially modify user allocations. Missing validation that the new merkle root maintains the same total allocation.
The function set_merkle_root
could be called by the owner whenever they want. There's no check that ensures that the previous allocation still exists and the total amount is the same.
It is possible that user could not claim
after the owner change the merkle root.
Consider limiting when the set_merkle_root
can be called. E.g. before vesting_start_time
The `set_merkle_root` function is called only by the `owner` and the `owner` is trusted. This means the input argument `merkle_root` will be correct and the `owner` will not call again the `set_merkle_root` function.
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.