The getAirdropToken function within the smart contract should be modified to return an address type instead of an interface type (IERC20). This adjustment ensures consistency in data types and enhances clarity and usability of the function.
The current implementation of the getAirdropToken function returns an interface type (IERC20) instead of an address type. While this may not necessarily lead to vulnerabilities, it introduces potential confusion and inconsistency in the codebase. Users interacting with the smart contract may expect a simple address value from the getAirdropToken function, but instead receive a more complex interface type. This discrepancy can lead to misunderstandings and errors in smart contract interactions.
The incorrect return type of the getAirdropToken function could affect the usability and understandability of the smart contract. Users may encounter difficulties in integrating the function into their applications or understanding its purpose due to the unexpected data type returned.
Manual Review
To address this issue, it is recommended to modify the getAirdropToken function to return an address type instead of an interface type (IERC20)
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.