V3 transaction policy for anti-pinning

[instagibbs]

@moonsettler

is there a reason to necessarily allow more than 1 unconfirmed ancestor for an ephemeral anchor type fee bump transaction?

I mean, it’d be nice for batched CPFP! There are no known designs to do that that are pin-resistant though.

@moonsettler

if only the anchor itself is unconfirmed, what mempool pinning tactics are possible?

not entirely sure what the question is, mind rewording?