Exploring Extended Relative Timelocks

The discussion focuses on the intricacies of utilizing specific bits within Bitcoin's Lightning Network for extending relative timelocks. A significant point raised is the current usage of these bits by Lightning to store obfuscated commitment transaction numbers, which essentially means that the bits with no consensus meaning might not be available as an upgrade hook for further developments. This highlights a limitation in leveraging the existing structure for enhancements without interfering with current functionalities.

Further exploration suggests that for anyone looking to work on extending relative timelocks, an alternative approach would be to utilize the Taproot annex. The proposal extends beyond just enhancing relative timelocks; it also encompasses integrating per-input absolute timelocks into a unified "improved timelocks" proposal. This approach not only addresses the technical challenge of extending timelocks but also suggests a cohesive strategy for broadening the scope of timelock functionalities within Bitcoin's framework, potentially leading to a more versatile and robust system.