[L-02] Missing Burned Event in burnFaucetTokens Reduces Transparency
Description: The burnFaucetTokens function transfers tokens from the contract to the owner and then burns a specified amount:
However, it does not emit any event to signal that a burn occurred. While _burn() internally emits a Transfer event to the zero address, this is not sufficient for tracking custom burn logic — especially since the tokens are first transferred to the owner before burning.
Impact:
-Reduced transparency: No clear signal that a burn was initiated by the owner.
-Harder auditing: External tools and users can’t easily track burn intent.
-Inconsistent event coverage: Other functions like mintFaucetTokens emit events, but burnFaucetTokens does not.
Recommended Mitigation:
Add a custom event to track burn actions:
Emit it after the burn:
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.