Tokens not compliant with the ERC20 specification could return false
from the transfer function call to indicate the transfer fails, while the calling contract would not notice the failure if the return value is not checked.
Checking the return value is a requirement, as written in the EIP-20
specification:
In LibPipelineConvert.sol#L53
:
.transfer
function is used instead of .safetransfer
function.
Returned value from transfer function is ignored.
Manual Analysis
It is recommended to use OpenZeppelin
’s SafeERC20 wrapper with the IERC20
interface to make the contracts compatible with currencies that return
no value.
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.