There is an acknowledgment that issues arise primarily when a revoked commit transaction gets confirmed on the network. Under such circumstances, one might find themselves in a competitive situation with the HTLC (Hashed Time-Locked Contracts) output spend. To address this problem, it's been suggested that implementing an additional relative delay for the SINGLE/ACP (SIGHASH_SINGLE/ANYONECANPAY) usage could be a viable solution. This approach, however, comes with the trade-off of requiring more signatures to be exchanged.

An important yet frequently underestimated advancement pertains to changes in version 3 (v3) of a certain protocol or software. A key benefit of these changes is the ability to allocate on-chain fees directly from the channel balance. This is seen as a significant improvement because it simplifies the fee-paying process by utilizing funds already within the channel, rather than relying on external sources. Furthermore, there is the possibility of using any non-pre-signed HTLC paths to cover transaction fees. For example, in a hypothetical scenario, a user named Bob could use the preimages from Alice's offered HTLCs to pay for his own transaction fees. This flexibility in managing fees showcases the evolving nature of smart contract functionality and the ongoing efforts to optimize blockchain transactions for efficiency and security.