From 3327552250abf910c3a9abfcdecd80d65aa29bb5 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Thu, 12 Mar 2026 13:44:58 -1000 Subject: [PATCH] Update 05_2_Resending_a_Transaction_with_RBF.md --- 05_2_Resending_a_Transaction_with_RBF.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/05_2_Resending_a_Transaction_with_RBF.md b/05_2_Resending_a_Transaction_with_RBF.md index 174f7dd..396130c 100644 --- a/05_2_Resending_a_Transaction_with_RBF.md +++ b/05_2_Resending_a_Transaction_with_RBF.md @@ -2,7 +2,7 @@ If your Bitcoin transaction is stuck, and you're the sender, you can _replace_ (resend) it using RBF (replace-by-fee). However, that's not all that RBF can do: it's generally a powerful and multipurpose feature that allows Bitcoin senders to recreate transactions for a variety of reasons. -## Opt-In RBF vs Full RBF +## Understand Opt-In RBF vs Full RBF There are currently two versions of RBF that are present on the Bitcoin network: opt-in RBF and full RBF. Both do the same thing: they allow you to replace an existing unconfirmed transaction with a newer transaction that has a higher fee (and so is more likely to be confirmed).