# 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:** 21

<div class="post-metadata">

**Author:** ![moonsettler](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/moonsettler/32/38_2.png) [@moonsettler](https://delvingbitcoin.org/u/moonsettler)\
**Post date:** [January 7, 2024, 9:00pm UTC](https://delvingbitcoin.org/t/v3-transaction-policy-for-anti-pinning/340/21 "2024-01-07T21:00:40Z")

</div>

> [@instagibbs](#):
>
> I mean, it’d be nice for batched CPFP! There are no known designs to do that that are pin-resistant though.

that’s what i thought. so first we could just allow for a more restricted and less efficient way of doing ephemeral anchors. but at least we would have something usable that is easy to implement and reason about. then expand later to more useful and more optimal ways of doing it?

---

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