[bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112)

Rusty Russell rusty at rustcorp.com.au
Fri Nov 27 04:02:45 UTC 2015


Eric Lombrozo via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> writes:
>>From an app developer's perspective, I think it is pretty blatantly 
> clear that relative timelock is *the* critical exposed functionality 
> intended here.

As someone who actually developed scripts using CSV, I agree with Mark
(and Matt).  The relative locktime stuff isn't in this opcode, it's in
the nSequence calculation.

So, I vote to keep CSV called as it is.

Thanks,
Rusty.


More information about the bitcoin-dev mailing list