Topic: TUTORIAL - How to fix Unconfirmed Transactions! (Read 326 times)

there is no such thing as "transaction booster". there are either scams that fool you into thinking you they have "boosted" your transaction speed while taking some money for something they didn't do; or they are legitimate big mining pools that would ask for a high price to prioritize your transaction which is not worth it since the cost is usually high.

Actually, there is another way called CPFP (child pays for parent).
The idea behind is, that you are going to use an unconfirmed output in a new transaction with a fee high enough for both transactions. Most miner will then simply include both of your transactions (because the average sat/B of your two transactions is worth it).

This can either be done by the receiver or by yourself if you didn't spend the output completely (i.e. there is a change output you can use).

Your only way is either:
1. transaction was RBF so you can put higher fee to it confirm faster
2. use transaction booster, some miners make tools like that available, but getting it free is hell you would need to pay a bit
3. wait

no other way here

Using some kind of transaction booster helps, I've used one in the past and it works but I don't see how this is a must, the fund you send out that failed to get included in a block will eventually get back into your wallet or eventually get confirmed, I sent out some eth four days ago and it got confirmed yesterday, it was because I used very small gas fee

Whether or not the new transaction has RBF enabled is irrelevant. That's the not the transaction you are trying to replace.

khaled0111 is correct. All that this method is doing is attempting to double spend your initial transaction. The vast majority of nodes are set up to reject double spend transactions, even those with higher fees than the original, you will likely be hit with a mempool conflict error when you try to broadcast your new transaction. Even if you do find a node which accepts it, then that node will almost certainly be unable to broadcast it to other nodes for the same reason.

Did you attempt this method? What was the outcome?

No, it's not working. The problem seems to be with the images hosting server used (postimg.org/) and not because of your rank.
Download the images from the original post and upload them to imgur or imgbb. It should fix the problem.

zapwallettxes will only remove unconfirmed transaction only from your node.

I was a newbie so the pictures didn't work, now everything is fine.
No, the method will work. It is like broadcasting the transaction using a full node with with -zapwallettxes -rescan flags

Note that the new transaction will be confirmed, old transaction will be rejected, and that the new transaction contains RBF flag.

Try it if you use old wallets like Blockchain.com, it will work.

The images you posted are not showing so please fix it.

Secondly, this method is probably not going to work as at the moment you broadcast the second transaction it will be rejected because of double spending.
What you did here is just deleting the transaction locally to let your wallet create a second transaction using the same inputs. However, the first transaction still exist in other nodes' mempools.

The only way this would work is if you send the signed transaction directly to cooperating miner or when the first transaction gets dropped from the network,s mempool.

I have a friend who accelerates my transactions but this one is a big help for those who are looking for ways to accelerate their transactions, last week was kinda hard the transaction is taking hours to confirm, you do this guide, request for acceleration or delay sending until the network gets better.

Read the topic again, ir shows you how to solve the problem without waiting for several days or weeks.
Even if you send from a wallet that does not support RBF. You will be able to receive confirmations at the same time after paying a higher fee.

Remove your spam reply

I guess you are referring to blockchain wallet; in electrum, RBF is available but you have to use RBF before broadcasting a tx. Since you initially used blockchain wallet, the tx wasn't RBF opt in. Either way, waiting couple of days would solve the problem too. You can remove tx onve it passes several days with unconfirmed status.

We all know that last week the fees were high, I had some transactions that I sent using Blockchain.com, but it was not confirmed for a long time.
I looked for a way to solve the problem, and I found this explanation.
I would like to share it with you.

https://steemit.com/bitcoin/@profitgenerator/tutorial-how-to-fix-unconfirmed-transactions

Requirements:
Unconfirmed transaction sent from wallet that does not support RBF.

The solution:

Import that wallet into Electrum, using private key or wallet seed.
We will do all the work on that wallet because it is easy to modify options in it.

Open that wallet using Electrum, you will notice the Unconfirmed transaction, but you can't do much because the wallet does not support RBF.



Disconnect the Internet, and do not return it until the last step to solve this problem.
Copy the hash of the transaction, by right clicking on it and copy. It should be a SHA-256 hash.
Create a Backup of the wallet. Be sure to do this step, problems may occur at any moment.
Open the wallet file with a text editor. The format of the wallet is JSON
Press CTRL-F on the keyboard, and search for this hash in the file

Do the following:


Delete between [] brackets + the coma above
Delete the TX hash
Delete everything between the {} bracket


Now open the wallet file, if it does, then you've finished the hard part.
If it does not work, repeat the above steps again.

Now sign a new transaction, but with a higher fee.
Reconnect to the Internet, sign this message through the file you created. And we're done.