In the protocol, the value of tx.locktime is only enforced if at least one input is non-final (NOT 0xFFFFFFFF sequence number). When executing require(tx.time >= <x>), this is automatically enforced, so currently, in order to safely use the value of tx.locktime, smart contract developers need to add a require(tx.time >= <x>) somewhere in their contract.
If a user uses tx.locktime, but no require(tx.time >= x) check exists within the branch where tx.locktime is accessed, then the compiler could add a require(tx.time >= 0) check to enforce the value.
In the protocol, the value of
tx.locktimeis only enforced if at least one input is non-final (NOT0xFFFFFFFFsequence number). When executingrequire(tx.time >= <x>), this is automatically enforced, so currently, in order to safely use the value oftx.locktime, smart contract developers need to add arequire(tx.time >= <x>)somewhere in their contract.If a user uses
tx.locktime, but norequire(tx.time >= x)check exists within the branch wheretx.locktimeis accessed, then the compiler could add arequire(tx.time >= 0)check to enforce the value.