From c60439aa5a430f33dd6e24414fe91b098a836a47 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Wed, 24 May 2017 15:01:01 -0700 Subject: [PATCH] Update 5_2_Resending_a_Transaction_with_RBF.md --- 5_2_Resending_a_Transaction_with_RBF.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5_2_Resending_a_Transaction_with_RBF.md b/5_2_Resending_a_Transaction_with_RBF.md index 4322c53..d834d22 100644 --- a/5_2_Resending_a_Transaction_with_RBF.md +++ b/5_2_Resending_a_Transaction_with_RBF.md @@ -8,7 +8,7 @@ If your Bitcoin transaction is stuck, and you're sender, you can resend it using ## Opt-In for RBF -RBF is an opt-in Bitcoin feature. Transactions are only eligible for using RBF if they've been created with a special RBF flag. This is done by setting a UTXO's sequence number (which is typically set automatically), so that it's more than 0 and less than 0xffffffff-1 (4294967294). +RBF is an opt-in Bitcoin feature. Transactions are only eligible for using RBF if they've been created with a special RBF flag. This is done by setting any of the transaction's UTXO sequence numbers (which are typically set automatically), so that it's more than 0 and less than 0xffffffff-1 (4294967294). This is accomplished simply by adding a `sequence` variable to your UTXO inputs: ```