Author: Mark Friedenbach 2015-10-06 00:19:06
Published on: 2015-10-06T00:19:06+00:00
The discussion on the bitcoin-dev mailing list revolves around the use of nSequence field in BIPs 68, 112, and 113. Peter Todd suggests that applications requiring relative CLTV should be implemented via nSequence. However, Alex Morcos questions whether this is the best way to use the nSequence field and proposes increasing granularity by reducing the resolution of the time-based sequence number locks to create more low-order bits. The use of RCLTV and OP_CSV is also discussed in the context of enforcing a delay between publishing a commitment transaction and spending the output in lightning commitment transactions. It is suggested that absolute CLTV alone can be used for bidirectional payment channels, but RCLTV is necessary for enforcing delays in lightning commitment transactions. The disadvantages of using nSequence/OP_CSV instead of RCLTV are highlighted, and it is suggested that OP_CRLTV alone can work for the use cases described in BIP68.
Updated on: 2023-06-10T23:45:12.348606+00:00