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

Rusty Russell rusty at rustcorp.com.au
Thu May 7 01:35:47 UTC 2015

Peter Todd <pete at petertodd.org> writes:
> That said, if people have strong feelings about this, I would be willing
> to make OP_CLTV work as follows:
>     <nLockTime> 1 OP_CLTV
> Where the 1 selects absolute mode, and all others act as OP_NOP's. A
> future relative CLTV could then be a future soft-fork implemented as
> follows:
>     <relative nLockTime> 2 OP_CLTV

Mildly prefer to put that the other way around.

ie. the OP_NOP1 becomes OP_EXTENSION_PREFIX, the next op defines which
extended opcode it is (must be a push).


More information about the bitcoin-dev mailing list