From fa9519c34623e21f014123f5e0ed08dcd1e07e94 Mon Sep 17 00:00:00 2001 From: claylock Date: Thu, 26 Oct 2023 18:49:57 +0000 Subject: [PATCH] Edited ch09_fees.adoc with Atlas code editor --- ch09_fees.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ch09_fees.adoc b/ch09_fees.adoc index ef7978bf..33268d05 100644 --- a/ch09_fees.adoc +++ b/ch09_fees.adoc @@ -566,6 +566,8 @@ transaction up to 1,000 vbytes in size can be added to a package even if it would exceed the other limits as long as it is a direct child of an unconfirmed transaction with no unconfirmed ancestors. +++++ +

For example, Bob and Mallory both co-sign a transaction with two outputs, one to each of them. Mallory broadcasts that transaction and uses her output to attach either 25 child transactions or any smaller @@ -574,7 +576,8 @@ carve-out, Bob would be unable to attach another child transaction to his output for CPFP fee bumping. With carve-out, he can spend one of the two outputs in the transaction, the one that belongs to him, as long as his child transaction is less than 1,000 vbytes in size (which should -be more than enough space). +be more than enough space).

+++++ It's not allowed to use CPFP carve-out more than once, so it only works for two-party protocols. There have been proposals to extend it to