I may be missing something, but I'm not sure how this changes anything?
If you have a commitment transaction, you always need at least, and
exactly, one non-CSV output per party. The fact that there is a size
limitation on the transaction that spends for carve-out purposes only
effects how many ot
Good morning list,
As is my wont, I again send unnecessary unsolicited spam on this list.
The Axiom of Terminus
=
Let us consider the below trivial Lightning Network:
A <-> B <-> C <-> D
There are three channels:
* AB
* BC
* CD
Now, let us consider, what happens if on
Reviving this old thread now that the recently released RC for bitcoind
0.19 includes the above mentioned carve-out rule.
In an attempt to pave the way for more robust CPFP of on-chain contracts
(Lightning commitment transactions), the carve-out rule was added in
https://github.com/bitcoin/bitcoin
