The `_safe_transfer and
_safe_transfer_from` functions are intended to safely transfer tokens. However, these functions do not handle the case where some ERC20 tokens do not return a boolean value upon a successful transfer. According to the ERC20 standard, some tokens may not return true on a successful transfer, and instead, they may just not revert. The current implementation assumes that a successful call must return true, which can lead to unnecessary transaction reverts for such tokens.
The current implementation may revert transactions for ERC20 tokens that do not return a boolean value upon a successful transfer. This can lead to failed transactions and a poor user experience when interacting with such tokens.
use safeERC20.sol
I believe the issues and duplicates do not warrant low severity severity as even if the call to transfers returns false instead of reverting, there is no impact as it is arguably correct given there will be insufficient funds to perform a rescue/withdrawal. This will not affect `tillIn()` as there are explicit balance [checks that revert accordingly](https://github.com/Cyfrin/2024-08-tadle/blob/04fd8634701697184a3f3a5558b41c109866e5f8/src/core/TokenManager.sol#L255-L260) to prevent allowing creation of offers without posting the necessary collateral
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.