CHECKSEQUENCEVERIFY - An opcode for relative locktime (Btc Drak)

2 messages, 13 Aug 2015. Started by Nicolas Dorier.

Nicolas Dorier, Matt Corallo

Nicolas Dorier 13 Aug 2015, 16:34 UTC permalink original

Would be wonderful to have this pushed together with CLTV and BIP68. If BIP68 get pushed in the next fork, this CSV is a no brainer.

Was there a competing RCLTV implementation somewhere that did not depend on BIP68 for information ? I don't manage to find it.

Matt Corallo 13 Aug 2015, 16:36 UTC in reply to Nicolas Dorier permalink original

On August 13, 2015 7:34:03 PM GMT+03:00, Nicolas Dorier via bitcoin-dev <bitcoin-dev@lists•linuxfoundation•org> wrote:

Quoted text (6 lines)

>Would be wonderful to have this pushed together with CLTV and BIP68.
>If BIP68 get pushed in the next fork, this CSV is a no brainer.
>
>Was there a competing RCLTV implementation somewhere that did not
>depend on
>BIP68 for information ? I don't manage to find it.

I think all such competing proposals are dropped because this seemed like a better idea. Feel free to revive one/come up with one, though.

Matt