crytic / crytic/building-secure-contracts
Mention somewhere that SafeIERC20 is strongly preferred
Open
- Dominant language
- Solidity
- Stars
- 2.5k
- Forks
- 391
- PR merge metrics
- No merged PRs in 30d
Description
[ERC20](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/IERC20.sol) vs [SafeIERC20](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/SafeERC20.sol)
Contributor guide
Research direction
Review the repository's training material and the linked IERC20 and SafeIERC20 contracts to identify the relevant ERC20 guidance. Add a clear note that SafeIERC20 is strongly preferred, and consider the issue complete when that preference is stated in the appropriate documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain, documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100