<p dir="ltr"><br>
On May 27, 2015 12:58 PM, "Peter Todd" <<a href="mailto:pete@petertodd.org">pete@petertodd.org</a>> wrote:</p>
<p dir="ltr">> What I'm not seeing is how the relative nLockTime that nSequence<br>
> provides fundamentally changes any of this.</p>
<p dir="ltr">This allows the implementation of a rcltv that doesn't make script depend on the current height, in a similar way that cltv uses the nLockTime (which has been compared with the current height already when checking the script).<br>
In fact, the implementation could be simpler if the goal of maintaining the original nSequence semantics was ignored ( although not that simpler, but you wouldn't need to use ~ (bitwise not).<br>
I'm still not sure whether there should be 2 BIPs for this or just one.</p>
<p dir="ltr">> --<br>
> 'peter'[:-1]@<a href="http://petertodd.org">petertodd.org</a><br>
> 000000000000000001643f7706f3dcbc3a386e4c1bfba852ff628d8024f875b6<br>
><br>
> ------------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
> <a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
><br>
</p>