From df71e510704e11cbe68064ed7d0de4d07f171f19 Mon Sep 17 00:00:00 2001 From: FIRSTNAME LASTNAME Date: Tue, 11 Apr 2017 15:09:43 +0200 Subject: [PATCH] Added links to following sections Signed-off-by: FIRSTNAME LASTNAME --- 5_1_Watching_for_Stuck_Transactions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/5_1_Watching_for_Stuck_Transactions.md b/5_1_Watching_for_Stuck_Transactions.md index 697886a..512001a 100644 --- a/5_1_Watching_for_Stuck_Transactions.md +++ b/5_1_Watching_for_Stuck_Transactions.md @@ -50,9 +50,9 @@ If your transaction is stuck longer than you want, you can typically do one of f **2. Wait Until it Expires.** If you accidentally sent with no transaction fee, or if any number or other conditions are met, then your transaction might never go through. However, your coins aren't lost. As long as you don't have a wallet that purposefully resends unconfirmed transactions, it should clear from the mempool in three days or so, and then you can try again. -**3. Use RBF as the Sender.** If you are the sender of the transaction, and you opted-in to RBF (Replace-By-Fee), then you can try again with a higher fee. +**3. Use RBF as the Sender.** If you are the sender of the transaction, and you opted-in to RBF (Replace-By-Fee), then you can try again with a higher fee ([see "Resending a Transaction with RBF"](5_2_Resending_a_Transaction_with_RBF.md)) -**4. Use CPFP as the Receiver.** Alternatively, if you are the receiver of the transaction, you can use CPFP (Child-pays-for-parent) to use the unconfirmed transaction as an input to a new transaction. +**4. Use CPFP as the Receiver.** Alternatively, if you are the receiver of the transaction, you can use CPFP (Child-pays-for-parent) to use the unconfirmed transaction as an input to a new transaction ([see "Funding a Transaction with CPFP"](5_3_Funding_a_Transaction_with_CPFP.md)). ## Summary: Watching for Stuck Transactios