Sequence

It is crucial to validate inputs, even if they come from trusted addresses, to avoid human error. A lack of robust input validation can only increase the likelihood and impact in the event of mistakes. Following is the list of places that can potentially benefit from stricter input validation: 1. qs-badge-acknowledged `ERC721Sale.sol`: the `cost` of the `setSaleDetails()` should not be zero. 2. qs-badge-fixed `ERC721Sale.sol`: the `endTime` of the `setSaleDetails()` should not be zero. 3. qs-badge-fixed `ERC721Sale.sol`: `setSaleDetails()` should validate that `startTime` is less than `endTime`. 4. qs-badge-acknowledged `ERC1155Sale.sol`: validate that `tokenIds` and `amounts` have the same length in `mint()`. 5. qs-badge-acknowledged `ERC20BaseToken.sol`: the `amount` of the `burn()` should not be zero. It is possible to burn zero amount of ERC-20 tokens with the current implementation. 6. qs-badge-acknowledged `ERC20Items.sol`: the `amount` of the `mint()` should not be zero. It is possible to mint zero ERC-20 tokens with the current implementation. 7. qs-badge-fixed `Orderbook._createOrder()` should validate that `request.tokenContract` and `request.currency` are not the zero address. 8. qs-badge-fixed `Orderbook.isOrderValidBatch()` should validate that `orderIds` and `quantities` are of equal length. 9. qs-badge-acknowledged `Trust.constructor()` should validate that `owner` and `beneficiary` are not set to the zero address.