arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-02-16 17:42:06 +00:00
Code Issues Releases Wiki Activity

Update ch09_fees.adoc

Browse Source 
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.
This commit is contained in:
Rafael Jan 2024-10-30 08:56:03 +02:00 committed by Rafael
parent 456adec1ee
commit 524458d3fd
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ch09_fees.adoc
View File

@ -474,7 +474,7 @@ transaction relationships. Whenever the output of a transaction is
spent, that transaction's identifier (txid) is referenced by the child spent, that transaction's identifier (txid) is referenced by the child
transaction. However, when a transaction is replaced, the replacement transaction. However, when a transaction is replaced, the replacement
has a different txid. If that replacement transaction gets confirmed, 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 possible to re-create and re-sign the descendant transactions, but that's
not guaranteed to happen. This has related but divergent implications not guaranteed to happen. This has related but divergent implications
for RBF and CPFP: for RBF and CPFP: