Replying to Avatar jimbocoin 🃏

Using nLockTime, you can mark a #Bitcoin transaction as invalid before some block height.

Is there yet a feature that does the reverse? That is, mark a transaction as invalid to include in any block AFTER a particular block height? #asknostr
Avatar
uncleJim21 2y ago

nostr:npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s

Reply to this note

Please Login to reply.

Discussion

Avatar
jimbocoin 🃏 2y ago

To my knowledge, covenants would enable confirmed transactions to include “can’t spend” conditions on outputs (such as block height), but thats not quite what I’m after.

I want to sign a transaction sends to regular addresses, but includes a stipulation that the whole TX is only valid if included before some height.

Avatar
Big Barry Bitcoin 2y ago

I don't think this exists. The issue I am thinking is that even if you send a transaction today, it might get confirmed next week... Heck it might get confirmed in a couple of months.

I've not thought too hard about this, but that might be the reason why it isn't possible.

Avatar
jimbocoin 🃏 2y ago

Agreed that the time-to-confirm is unbounded. Nevertheless, I believe it’s within the realm of possibility for there to be such a feature. I’m fairly certain such a feature does not yet exist (and I’m aware of no proposals).