# Lightning transactions with v3 and ephemeral anchors

**URL:** <https://delvingbitcoin.org/t/lightning-transactions-with-v3-and-ephemeral-anchors/418>\
**Category:** Protocol Design\
**Tags:** mempool, lightning\
**Created:** [January 16, 2024, 5:28pm UTC](https://delvingbitcoin.org/t/lightning-transactions-with-v3-and-ephemeral-anchors/418 "2024-01-16T17:28:44Z")\
**Posts on this page:** 1\
**Showing post:** 18

<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:** [January 18, 2024, 2:39pm UTC](https://delvingbitcoin.org/t/lightning-transactions-with-v3-and-ephemeral-anchors/418/18 "2024-01-18T14:39:43Z")

</div>

> [@t-bast](#):
>
> Can you describe that in more details?

Hm right, I guess this would only matter if the revoked commit tx _gets confirmed_. In that case you may have to compete with the HTLC output spend, which is why @ajtowns is suggesting an additional relative delay for SINGLE/ACP usage, at the cost of more signatures exchanged.

edit: I’m wrong and tbast is right, look at reply

> [@t-bast](#):
>
> Yes, that is a very nice benefit of the v3 change! Being able to pay the on-chain fees directly from the channel balance is a very important but often overlooked improvement in my opinion.

[Remove all the `1 OP_CHECKSEQUENCEVERIFY OP_DROP` please!](https://github.com/instagibbs/bips/blob/d33cdbd0777700f4fc488d54b90a8795d2c33639/bip-ephemeralanchors.mediawiki#expected-use-cases)

You could also use any non-pre-signed HTLC paths for fees as well. e.g., Bob could sweep Alice’s offered HLTCs with preimage and use those towards fees.

---

_[View the full topic](https://delvingbitcoin.org/t/lightning-transactions-with-v3-and-ephemeral-anchors/418)._