|
|
|
@ -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
|
|
|
|
|