Expiring HTLCs without free relay

The email outlines several aspects of current blockchain transaction management and potential improvements. The sender was initially under the assumption that most implementations involved mempool monitoring, which turns out not to be the case. They express surprise over this discovery and shift focus to other methods, such as grinding and rebroadcasting. However, their main aim with the proposal discussed is to introduce relay-safe expiry to counteract what they describe as the time-sensitive replacement cycling attack. This approach could also potentially remove the need for previous methods like grinding and rebroadcasting.

In addition, the discussion includes a reference to a suggestion by @ajtowns regarding the reconsideration of the 100 block delay currently in place in OP_EXPIRE. The sender included this delay in their proposal as a conservative measure, aiming to align with existing protocols. However, they hint at possible changes where consensus and relay operations might remain stable even with a significantly reduced delay. For further details on this aspect, the sender refers to a specific post by @ajtowns, which can be accessed here.

The sender concludes with plans to delve deeper into these issues in a future blog post, suggesting ongoing research and discussion in this area. This reflects an active engagement with evolving blockchain technologies and the continuous search for enhancements in transaction management protocols.