The Standard

Summary

Use SafeERC20Upgradeable instead of SafeERC20 for upgradeable contract.

Vulnerability Details

SafeERC20 and SafeERC20Upgradeable are the same. The reasons SafeERC20 was renamed to SafeERC20Upgradeable was:

• to make it clear that the code is safe for upgradeability, and

• to avoid potential clashes with the original one.

Either of the two can be used. However. it's bettter to use SafeERC20Upgradeable if Openzeppelin's Upgrades plugins isn't used to check for safety.

See: https://forum.openzeppelin.com/t/safeerc20-vs-safeerc20upgradeable/17326

In this instance, it's unknown if Openzeppelin's Ugrades plugins is used or will be used.

Impact

Using SafeERC20Upgradeable for upgradeable contracts gives better guarantee of safety.

Tools Used

Manual review

Recommendations

Use SafeERC20Upgradeable