Analysis of attempting to imbue LN commitment transaction spends with v3 semantics

[instagibbs]

@t-bast

and even without changing anything, if the transaction is rejected from our mempool, we automatically retry funding it at the next block, so we would very likely eventually fund with a confirmed input (unless none are available of course).

This is my hope, that every LN implementation will just keep trying with different input sets, and also stop trying to do batched operations if things aren’t confirming.