The SnowmanAirdrop contract should efficiently manage storage and only allocate gas for variables that are actively used in the contract logic.
The s_claimers array is declared to store addresses of claimers but is never populated throughout the contract, resulting in wasted gas for storage allocation.
The contract declares a storage array for tracking claimers but fails to utilize it, creating unnecessary gas costs without providing any functionality.
The claimSnowman() function processes claims but never adds addresses to the s_claimers array 2 .
Reason 1: The array is declared in storage but never written to during contract execution
Reason 2: No functions read from or modify the s_claimers array
Impact 1: Unnecessary gas costs for storage slot allocation during deployment
Impact 2: Confusing code structure that suggests functionality that doesn't exist
Impact 3: Potential future maintenance issues if developers assume the array is being used
Alternatively, if claim tracking is desired, implement proper functionality:
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.