# Improving transaction sponsor blockspace efficiency

**URL:** <https://delvingbitcoin.org/t/improving-transaction-sponsor-blockspace-efficiency/696>\
**Category:** Protocol Design\
**Tags:** mempool, softfork\
**Created:** [March 19, 2024, 6:58pm UTC](https://delvingbitcoin.org/t/improving-transaction-sponsor-blockspace-efficiency/696 "2024-03-19T18:58:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![reardencode](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/reardencode/32/27_2.png) [@reardencode](https://delvingbitcoin.org/u/reardencode)\
**Post date:** [March 19, 2024, 7:22pm UTC](https://delvingbitcoin.org/t/improving-transaction-sponsor-blockspace-efficiency/696/2 "2024-03-19T19:22:22Z")

</div>

As I [posted](https://twitter.com/reardencode/status/1770094336434430157) on X, the biggest complication with sponsors is that the sponsor transaction can become invalid depending on innocent block reorderings, which would require it to be treated as a coinbase output and mature before it can be used in a normal transaction. I think this prevents sponsorship from being done as a part of regular transaction operations.

That said, sponsors (or other transactions that are provably re-bindable to either a current txo or one of its ancestors) could be allowed to spend before maturation, which means that a dedicated sponsor TXO could be spent repeatedly without maturing between spends, and only a subsequent spend that would not be re-bindable would have to wait for maturity.

---

_[View the full topic](https://delvingbitcoin.org/t/improving-transaction-sponsor-blockspace-efficiency/696)._