Describe the normal behavior in one or more sentences
The `set_deadline` function accepts any `u64` value as a deadline without validating that it represents a future timestamp. This allows creators to set deadlines in the past, which would immediately make the fund inactive and prevent contributions.
Explain the specific issue or problem in one or more sentences
The normal behavior should ensure that deadlines are set to future timestamps, preventing creators from accidentally or maliciously setting invalid deadlines. The current implementation accepts any value.
Likelihood:
* This occurs when creator accidentally sets a past timestamp
* This occurs when creator maliciously sets deadline to prevent contributions
* Happens when timestamp conversion errors occur
Impact:
* Fund becomes immediately inactive if past deadline is set
* Contributors cannot contribute to funds with past deadlines
* Creator may need to create a new fund if deadline is set incorrectly
* Potential DoS if deadline is set maliciously
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.