Lightning transactions with v3 and ephemeral anchors

[t-bast]

@glozow

I suppose both are doable, though the question for me is less “how can we identify a (LN) anchor spend?” and more “how can we identify users of CPFP carve out?” At the end of the day we’re trying to continue supporting CPFP carve out as long as possible, for applications that don’t explicitly set nVersion=3 right?

I misunderstood then, I thought it wouldn’t be possible to keep supporting the CPFP carve-out logic alongside cluster mempool code. That’s why I thought the only option was to implicitly enroll the only users of CPFP carve-out (lightning commitment txs containing two anchor outputs) to the v3 policies to replace CPFP carve-out entirely.