The burnToken function in the LibTransfer library calls LibTransfer.receiveToken instead of calling the receiveToken function directly, despite receiveToken being available within the same contract. This practice introduces unnecessary complexity and potential readability issues.
See the following code:
The receiveToken function is called with the LibTransfer prefix, despite being available within the same contract. This approach:
It makes the code less readable and can confuse developers about the origin and scope of the function.
The use of the LibTransfer prefix is redundant and unnecessary since the function is part of the same library.
Manual Reivew
The function receiveToken should be called directly within the burnToken function, removing the unnecessary LibTransfer prefix. This will improve the readability and maintainability of the code.
Invalid as per docs https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity
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.