1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-21 23:58:09 +00:00

Edited ch09_fees.adoc with Atlas code editor

This commit is contained in:
claylock 2023-10-26 18:49:57 +00:00
parent 34b26984ee
commit fa9519c346

View File

@ -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 it would exceed the other limits as long as it is a direct child of an
unconfirmed transaction with no unconfirmed ancestors. unconfirmed transaction with no unconfirmed ancestors.
++++
<p class="fix_tracking">
For example, Bob and Mallory both co-sign a transaction with two For example, Bob and Mallory both co-sign a transaction with two
outputs, one to each of them. Mallory broadcasts that transaction and outputs, one to each of them. Mallory broadcasts that transaction and
uses her output to attach either 25 child transactions or any smaller 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 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 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 as his child transaction is less than 1,000 vbytes in size (which should
be more than enough space). be more than enough space).</p>
++++
It's not allowed to use CPFP carve-out more than once, so it only works 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 for two-party protocols. There have been proposals to extend it to