TokenTimelock - dangerous comparaison

Smart Contracts
1

Hello,

We are running Slither on a openZepplin contract.
We get the following :

TokenTimelock.constructor(IERC20,address,uint256) (node_modules/@openzeppelin/contracts/token/ERC20/utils/TokenTimelock.sol#32-41) uses timestamp for comparisons
Dangerous comparisons:

  • require(bool,string)(releaseTime_ > block.timestamp,TokenTimelock: release time is before current time) (node_modules/@openzeppelin/contracts/token/ERC20/utils/TokenTimelock.sol#37)
    TokenTimelock.release() (node_modules/@openzeppelin/contracts/token/ERC20/utils/TokenTimelock.sol#68-75) uses timestamp for comparisons

Are there any solutions ?

1 Like
2

I am also facing a similar issue on one of my comparison statement,

require(_tokenLockMapping[_tokenId] != uint256(TokenLockStatus.LOCKED),"Fail")

Not sure, why is this..