In _transfer is called to transfer _amount of _tokenAddress from _accountAddress to capitalPoolAddr. However, there is no mechanism to handle the scenario where the actual amount transferred is less than expected due to slippage.Without slippage control, the function might assume the full _amount was transferred, which could lead to inconsistencies in the contract’s state or unexpected behavior.
The lack of checks for slippage during ERC20 token transfers could lead to inaccurate balances and potential underfunding of the capitalPoolAddr.
If the transferred amount is less than _amount, this could result in the contract overestimating the balance in the capitalPoolAddr, which could lead to issues in accounting or underfunding for subsequent operations.
Vscode
To handle slippage, the function should include a check after the transfer to verify that the expected _amount was actually transferred. If not, the transaction should revert.
Invalid, these are by default, invalid based on codehawks [general guidelines](https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity#findings-that-may-be-invalid). The check implemented is simply a sufficiency check, it is users responsibility to only send an appropriate amount of native tokens where amount == msg.value when native token is intended to be used as collateral (which will subsequently be deposited as wrapped token). All excess ETH can be rescued using the `Rescuable.sol` contract. > Users sending ETH/native tokens > If contracts allow users to send tokens acc111identally.
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.