# Input-triggered transaction expiry

**URL:** <https://delvingbitcoin.org/t/input-triggered-transaction-expiry/2667>\
**Category:** Protocol Design\
**Tags:** softfork, expiry\
**Created:** [June 29, 2026, 1:13am UTC](https://delvingbitcoin.org/t/input-triggered-transaction-expiry/2667 "2026-06-29T01:13:38Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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, 5:08pm UTC](https://delvingbitcoin.org/t/input-triggered-transaction-expiry/2667/6 "2026-06-29T17:08:21Z")

</div>

@ademan

> [@josh](#):
>
> `CLTV` enforces a minimum `nLockTime`, so I don’t believe this works. We need to enforce a maximum `nLockTime`. This is probably best accomplished with `nLockTime` introspection (ex: `OP_LOCKTIME`) and `OP_LESSTHAN`.

I believe he meant in conjunction with `OP_TX` and math on the stack

---

_[View the full topic](https://delvingbitcoin.org/t/input-triggered-transaction-expiry/2667)._