The WeatherNft contract accepts various parameters in its constructor to configure the contract and initialize key variables.
The _keeperRegistry
parameter is declared and assigned to state variable s_keeperRegistry
, but this state variable is never used anywhere in the contract's logic.
Likelihood: Low
The issue is present in deployed code and will affect all instances
The code compiles and functions correctly despite the unused parameter
Impact: Low
Introduces unnecessary gas costs during contract deployment due to storing an unused address
Creates confusion for developers maintaining or interacting with the system
May indicate incomplete or abandoned functionality that was intended for the contract
The state variable s_keeperRegistry
is assigned in the constructor but no function in the contract reads or uses this value:
Either remove the unused parameter or implement its intended functionality:
Option 1 - Remove the unused parameter:
Option 2 - Document its purpose if it's intended for future functionality:
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.