Issue K: Unsafe ERC20 Token Transfer #762
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Fix issue #133
Location
/nightfall-deployer/contracts/Shield.sol
Synopsis
ERC20 tokens transfer and transferFrom are unsafe methods for token transfers that do not adhere to the IERC20 standard of reverting in the case of failure. In some cases, these methods may cause tokens to be locked in the contract.
Impact
User funds may potentially get locked in the contract.
Remediation
We recommend the use of the standard safe transfer wrapper by OpenZeppelin.
Done
SafeERC20Upgradeable
from OpenZeppelin as it's compatible with our upgradeable contracts.safeTransfer
andsafeTransferFrom
.Refactor
ERCInterface.sol
contract.ERCStub.sol
,ERC721_2Mock.sol
andERC1155_2Mock.sol
mocks contracts.mocks
folder in contracts innightfall-developer
.