# Throughout code base, implement using SafeERC20 for IERC20 for better readability Low/Info · Three Sigma · Lending aggregator · 6th May, 2023 Finding 3S-FUJI-N03 of the Fuji Finance security review. - Report: /reports/fuji-finance - Source: https://cdn.sanity.io/files/qoqld077/staging/32181a28eac3175d15fb8924d249bb0d91ca350c.pdf --- ### Description When using SafeERC20, it's common to implement with using SafeERC20 for IERC20. Take a look at the [openzeppelin code](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/utils/SafeERC20.sol#L16). ### Status Addressed here: [Fujicracy/fuji-v2#648](https://github.com/Fujicracy/fuji-v2/pull/648) --- Related findings: - [`IDORoundConfig.idoPrice` could have a comment somewhere specifying the units for better readability](https://0xsimao.com/findings/blast-ido-pools-round-price-somewhere-specifying): Blast IDO Pools - [Admin checks in KeyringCoreV2Base could be placed in a modifier to increase readability and reduce code duplication](https://0xsimao.com/findings/keyring-ii-placed-readability-reduce-duplication): Keyring Credentials - [Throughout code-base: Homogenize how access control is done.](https://0xsimao.com/findings/maple-finance-iii-homogenize-access-control-done): Maple Finance - [Throughout code base: use Solidity native errors implementation instead of string errors.](https://0xsimao.com/findings/maple-finance-iii-solidity-native-implementation-string): Maple Finance