From ecec5f401b49cebb949664eea15f5e26b81a3ef7 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 14:12: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 785afb4c..e9d5e23c 100644 --- a/ch09_fees.adoc +++ b/ch09_fees.adoc @@ -212,7 +212,7 @@ transaction to pay a higher total fee than the original transaction, but this requirement has undesired side effects and developers have been looking for ways to remove it at the time of writing. -Bitcoin Core((("Bitcoin Core", "RBF variants"))) currently supports two variations of RBF: +Bitcoin Core((("Bitcoin Core", "RBF variants", id="bitcoin-core-rbf"))) currently supports two variations of RBF: Opt-in RBF:: An unconfirmed transaction can signal to miners and full nodes that @@ -283,7 +283,7 @@ added an option that allows users to enable full RBF. If enough mining hash rate and relaying full nodes enable this option, it will be possible for any unconfirmed transaction to eventually be replaced by a version paying a higher fee rate. As of this writing, it's not clear -whether or not that has happened yet. +whether or not that has happened ((("Bitcoin Core", "RBF variants", startref="bitcoin-core-rbf")))yet. **** As a user, if you plan to use RBF fee bumping, you will first need to