# Expiring HTLCs without free relay

**URL:** <https://delvingbitcoin.org/t/expiring-htlcs-without-free-relay/2663>\
**Category:** Protocol Design\
**Tags:** lightning, softfork, expiry\
**Created:** [June 27, 2026, 10:27pm UTC](https://delvingbitcoin.org/t/expiring-htlcs-without-free-relay/2663 "2026-06-27T22:27:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![instagibbs](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/instagibbs/32/28_2.png) [@instagibbs](https://delvingbitcoin.org/u/instagibbs)\
**Post date:** [June 29, 2026, 1:53pm UTC](https://delvingbitcoin.org/t/expiring-htlcs-without-free-relay/2663/2 "2026-06-29T13:53:58Z")

</div>

Thanks for the interesting idea! Not having to worry about free relay is a nice benefit.

> [@josh](#):
>
> Unlike `OP_EXPIRE`, this approach does _not_ prevent replacement cycling in the refund path. Instead, it eliminates the economic incentive to attack by guaranteeing an eventual refund in the absence of timely preimage publication. Either a routing node has sufficient opportunity to claim the inbound funds, or they have a guaranteed claim to a refund.

Took me a while to get the claim, probably should have started with this. Many implementations do no mempool monitoring at all, so I was confused what this was accomplishing. What the claim is is that with proper expiry, replacement cycling is a just a more time insensitive grief vector, which makes the mempool scanning some may do as a partial mitigation, like LND , completely unnecessary. Wtxid grinding and rebroacasting also become unnecessary at least in theory (I think there are valid reasons to do it anyway)

---

_[View the full topic](https://delvingbitcoin.org/t/expiring-htlcs-without-free-relay/2663)._
