From 69d139d501852432044cee19c25652992ee52df2 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 14:15:17 +0000 Subject: [PATCH] Edited ch09_fees.adoc with Atlas code editor --- ch09_fees.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch09_fees.adoc b/ch09_fees.adoc index 393afd97..16a53117 100644 --- a/ch09_fees.adoc +++ b/ch09_fees.adoc @@ -377,14 +377,14 @@ profitable to confirm both of them in the same block. To evaluate the profitability of mining both a parent and child transaction, the miner looks at them as a _package of transactions_ with an aggregate size and aggregate fees, from which the fees can be divided -by the size to calculate a _package fee rate_. The miner can then sort +by the size to calculate((("package fee rate"))) a _package fee rate_. The miner can then sort all of the individual transactions and transaction packages they know about by fee rate and include the highest-revenue ones in the block they're attempting to mine, up to the maximum size (weight) allowed to be included in a block. To find even more packages that might be profitable to mine, the miner can evaluate packages across multiple generations (e.g., an unconfirmed parent transaction being combined with -both its child and grandchild). This is called _ancestor fee rate +both its child and grandchild). This is ((("ancestor fee rate mining")))called _ancestor fee rate mining_. Bitcoin Core has implemented ancestor fee rate mining for many years,