[Bitcoin-development] CLTV opcode allocation; long-term plans?

Luke Dashjr luke at dashjr.org
Tue May 12 20:38:27 UTC 2015

It should actually be straightforward to softfork RCLTV in as a negative CLTV.
All nLockTime are >= any negative number, so a negative number makes CLTV a 
no-op always. Therefore, it is clean to define negative numbers as relative 
later. It's also somewhat obvious to developers, since negative numbers often 
imply an offset (eg, negative list indices in Python).


More information about the bitcoin-dev mailing list