delvingbitcoin
Contract-level Relative Timelocks (or, let's talk about ancestry proofs and singletons)
Posted on: January 13, 2025 19:42 UTC
In a recent discussion, the intricacies of Hashed Timelock Contracts (HTLC) settlements on the Lightning Network (LN) were explored.
The primary focus was on the maximum duration an HTLC could take to settle, which is identified as twice the shared_delay
period. This timeframe is critical for ensuring that transactions are completed successfully without undue delay or vulnerability to malicious activities.
The conversation also touched upon the potential for abuse by a channel partner who might attempt to broadcast new update transactions beyond the established 2x shared_delay
window. To counteract this, it was suggested that Symmetry HTLCs should have longer expiration times than Penalty HTLCs. This strategy aims not only to safeguard against possible attacks but also to enhance the efficiency of capital utilization within the LN framework.
Furthermore, it was clarified that the implementation of CLRT (Commitment-Lightning Round Trip) protocols is not specifically designed to address any direct attack vectors. Instead, CLRT's primary purpose is to optimize the use of capital within the Lightning Network by ensuring timely and secure transaction settlements. This approach underscores the ongoing efforts to refine and improve the operational efficiency of LN, making it a more robust and reliable platform for users.