From d140423abaad9a0ebaf3ac4683532570c0e971a3 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 14:10:04 +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 be30f83a..eb6fc397 100644 --- a/ch09_fees.adoc +++ b/ch09_fees.adoc @@ -193,7 +193,7 @@ bumping in Bitcoin, replace by fee (RBF) and child pays for parent [[rbf]] === Replace By Fee (RBF) Fee Bumping -To increase the fee of a transaction using RBF fee bumping, you create +To((("transaction fees", "fee bumping", "RBF (replace by fee)", id="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", id="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", id="rbf"))) increase the fee of a transaction using RBF fee bumping, you create a conflicting version of the transaction that pays a higher fee. Two or more transactions are considered to be _conflicting transactions_ if only one of them can be included in a valid blockchain, forcing a miner @@ -354,7 +354,7 @@ general, if you're the receiver of an unconfirmed transaction and you want to make it confirm faster (or at all), you can't use an RBF fee bump; you need some other method. -There are additional problems with RBF that we'll explore in <>. +There are additional problems ((("transaction fees", "fee bumping", "RBF (replace by fee)", startref="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", startref="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", startref="rbf")))with RBF that we'll explore in <>. [[cpfp]] === Child Pays for Parent (CPFP) Fee Bumping