From 524458d3fdb44de1ed914613357a406baf5a585f Mon Sep 17 00:00:00 2001 From: Rafael Jan Date: Wed, 30 Oct 2024 08:56:03 +0200 Subject: [PATCH] Update ch09_fees.adoc The text "none of its descendants can be included in the same blockchain" is misleading. Because it actually can't be included in any blockchain. I think it should be "all of its descendants will be invalid", because now the txid that descendants are using is invalid and can't be used in any blockchain. --- ch09_fees.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch09_fees.adoc b/ch09_fees.adoc index 6eedacb1..c09291b1 100644 --- a/ch09_fees.adoc +++ b/ch09_fees.adoc @@ -474,7 +474,7 @@ transaction relationships. Whenever the output of a transaction is spent, that transaction's identifier (txid) is referenced by the child transaction. However, when a transaction is replaced, the replacement has a different txid. If that replacement transaction gets confirmed, -none of its descendants can be included in the same blockchain. It's +all of its descendants will be invalid. It's possible to re-create and re-sign the descendant transactions, but that's not guaranteed to happen. This has related but divergent implications for RBF and CPFP: