# V3 transaction policy for anti-pinning

**URL:** <https://delvingbitcoin.org/t/v3-transaction-policy-for-anti-pinning/340>\
**Category:** Protocol Design\
**Tags:** lightning, pinning, mempool\
**Created:** [January 2, 2024, 9:31am UTC](https://delvingbitcoin.org/t/v3-transaction-policy-for-anti-pinning/340 "2024-01-02T09:31:41Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![harding](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/harding/32/925_2.png) [@harding](https://delvingbitcoin.org/u/harding)\
**Post date:** [January 5, 2024, 9:54pm UTC](https://delvingbitcoin.org/t/v3-transaction-policy-for-anti-pinning/340/14 "2024-01-05T21:54:25Z")

</div>

> [@nettimel](#):
>
> Link to what a HTLC-X transaction is?

@instagibbs is talking about HTLC-Success and HTLC-Timeout transactions as defined in [BOLT3](https://github.com/lightning/bolts/blob/8a64c6a1cef979b3f0cecb00ba7a48c2d28b3588/03-transactions.md)

These are presigned spends of HTLCs made with `SIGHASH_SINGLE|SIGHASH_ANYPREVOUT` that allow multiple of them to be combined into a single transaction. The don’t contribute any fee (or any meaningful fee), so we would normally expect them to be combined with an extra contributed input that adds fees (and likely an extra output for change). However, the threat-to-decentralization argument, you could pay a miner out-of-band fees to mine them without adding an extra input or output, saving block space.

I made this same argument to PT last night (last paragraph): [https://twitter.com/hrdng/status/1743293516992876561](https://twitter.com/hrdng/status/1743293516992876561)

---

_[View the full topic](https://delvingbitcoin.org/t/v3-transaction-policy-for-anti-pinning/340)._
