Several state variables are declared and initialized but never updated or used:
totalPenaltyFeesCollected - Always remains 0
addressTotalSwaps - Mapping is never written to
addressPenaltyCount - Mapping is never written to
Likelihood:
These unused variables exist in every deployment
Impact:
Extra gas cost for storage slot initialization (cold storage access)
Misleading public interface - external parties may expect these to contain data
Code suggests penalty tracking exists when it doesn't
Potential confusion in audits and integrations
Execute 5 penalty-triggering swaps - all tracking variables remain 0.
Remove unused variables or implement actual tracking.
Option 1: Remove unused variables
Option 2: Implement the tracking (if intended)
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.
The contest is complete and the rewards are being distributed.