From 48d94c8c0610f8d084770a56e3b81b8068ab8f90 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Thu, 2 Apr 2026 07:42:19 -1000 Subject: [PATCH] renumber --- 06_0_Controlling_Bitcoin_Transactions.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/06_0_Controlling_Bitcoin_Transactions.md b/06_0_Controlling_Bitcoin_Transactions.md index 81ccb12..bd88f84 100644 --- a/06_0_Controlling_Bitcoin_Transactions.md +++ b/06_0_Controlling_Bitcoin_Transactions.md @@ -1,4 +1,4 @@ -# Chapter Five: Controlling Bitcoin Transactions +# Chapter Six: Controlling Bitcoin Transactions Sending a transaction isn't always the end of the story. Using the RBF (replace-by-fee) and CPFP (child-pays-for-parent) protocols, a developer can continue to control the transaction after it's been sent, to improve efficiency or to recover transactions that get stuck. These methods will begin to spotlight the true power of Bitcoin. @@ -18,6 +18,6 @@ Supporting objectives include the ability to: ## Table of Contents - * [Section One: Watching for Stuck Transactions](05_1_Watching_for_Stuck_Transactions.md) - * [Section Two: Resending a Transaction with RBF](05_2_Resending_a_Transaction_with_RBF.md) - * [Section Three: Funding a Transaction with CPFP](05_3_Funding_a_Transaction_with_CPFP.md) + * [Section One: Watching for Stuck Transactions](06_1_Watching_for_Stuck_Transactions.md) + * [Section Two: Resending a Transaction with RBF](06_2_Resending_a_Transaction_with_RBF.md) + * [Section Three: Funding a Transaction with CPFP](06_3_Funding_a_Transaction_with_CPFP.md)