In the documentation, it was written that it allows authorized claimants 90 days to claim before the manager takes cut of the remaining pool. But this was not so.
The `claimCut` function in the contract allows participants to claim their rewards even after 90 days have passed since the contest deployment. This occurs because the function does not include any time-based restrictions or checks to prevent claims after the designated period has ended. The only restriction that could prevent such claims is if the `closeContest` function is called, which would prevent further claims. However, if by any chance the `closeContest` function is not called immediately after 90 days due to certain reasons, participants can continue to claim rewards indefinitely, which is contrary to the intended functionality of the contract breaking a key invariant.
This was suppose to revert because the claiming period has ended but it didnt. So it means a user can claim even after the 90 days if the `closePot` isnt called
When the `closePot` function is called later than intended, the manager's cut is shortened and also the ClaimantCut is also reduced.
Extended Claim Period: Ineligable claimants can claim rewards beyond the intended 90-day window, which by initial plan wasnt allowed. This can break the trust in the protocol and rightful claimants can lose integrity for the protocol.
Unintended Fund Drain: If participants can claim rewards after the intended claim period, they could deplete the contract's funds over time, potentially exhausting the reward pool before the contest can be properly closed.
Manual Review
Foundry Testing
Here is our Modified fuction with the check:
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.