When a participant changes their participation status from true to false, and then deposits funds to the contract again, it will emit a NewSignUp event which is technically not true as the user had already Signed up previously and did not refund his funds. It's more like a Re-Signing up.
Incorrect or missing events can hinder off-chain monitoring and cause issues with integrations
Manual Review
add a new event such as:
And then change the emission logic of the deposit() and receive() functions for better clarification:
So that now if a participant redeposits after changing their status to false it will emit a ReSignupevent making the phenomenon clearer.
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.