Topic: Unconfirmed transaction (Read 293 times)

Those set of replies deviated from the original topic and the thread must be referring to Electrum's "cancel transaction"
which isn't the case in Bitcoin Core's "abandon transaction".

In Bitcoin Core, the mentioned right-click menu option on the specific transaction in the 'Transactions' tab will be clickable once it's dropped from your mempool.
That will drop it from your wallet (marked with a trash can icon) and by doing so, the wallet will let you use the UTXOs that it tried spend to another transaction.
That's posted in the first page.
If it's still unavailable:

• Close Bitcoin Core.
• Go to its datadir (if you didn't set a custom datadir: Default Location)
• Delete "mempool.dat" file.
• In the same datadir, open you bitcoin.conf file as text; create one if you don't have one (make sure that the extension is '.conf' and not '.conf.txt')
• Type walletbroadcast=0 and save.
• Start Bitcoin Core and abandon transaction should be available, use it.
• Create a new transaction, after that, close Bitcoin Core, remove walletbroadcast=0, then start Bitcoin Core again.

I got your point on the use-case of main-chain transactions though.
But read my reply to your other topic: https://bitcointalksearch.org/topic/m.64560505

You can still increase the fee with RBF in this case, it will just reduce the amount received by the destination output. I'm not sure how to do it with Core though, it's a part of the standard speedup behavior in Wasabi Wallet.

I'm using Bitcoin Core.
It's an address from long time ago with quite a few transactions (I used to play and participated in a lot of bitcoin marketplace for fun when I was in college). The total transaction total size came up to 17243 bytes. So, even with 1/vKB, transaction fee came up to 0.00017243 BTC. Left the BTC marketplace since then; therefore wallet has a small amount.

When I make the recent transfer out, I used the total amount minus the fee with $0.00000000 left in the wallet. Therefore, RBF (replace-by-fee) or increasing the fee is not an option because the wallet essentially has 0 satoshi left.

I haven't been using / following BTC besides the brief period in the early days (without aging myself) and totally unfamiliar with most of the terminologies. I apologize. Therefore, I'm not sure how else (besides waiting) for the return and re-issue the transaction. Anywhere anyone can point me to request for the return would be great.

Thank you


Exactly the situation. Don't know how to thumbs up; but, appreciate the understanding.
Hence, the conundrum. And function of BTC besides an invest-able asset class. The early original idea of replacing fiat is not feasible.

I do not know bitcoin core very well, else I would've known the possibility of setting the right fee rate. In electrum, there's a level of fee rate you would set and it would inform you its too low, then you need to increase it if you want your transactions confirmed on time.

Cancelling a transaction is the same process as double spending it to the destination address, you bump the fee and spend it back to your wallet and in the end only enrich the miners and achieve nothing, so its better to bump the fee and send it to the destination address, but in the case of OP, he has literally no spare and he would have to wait for as long as it takes for it to drop back to the wallet if at all it would happen, unless he deposits some coins into the wallet to bump the fee, but in his case it makes no sense since the funds he is sending across is very little.

OP didn't say the transaction was made a long time ago. OP said that he had some bitcoin from a long time ago and he made a transaction recently.


The fees have become lower in the past days, but it's not that only 1 sat/vbyte transactions couldn't be confirmed. In the past 8 months, no transactions paying less than 3 sat/vbyte as fee have been confirmed normally.

You are right that without the TX ID it will be hard for anyone to give the to the point solution.  Also these days the TX fee is very low as OP mentioned he made a transfer a long time back, most probably his transaction must have been confirmed.
The only reason i see that it can still be unconfirmed if he has used 1Sat/vbyte as the fee 

Without knowing what fee rate you used or sharing the TX ID here. Members are just making a few guesses here and there on what the problem could be. Search your transaction ID using a wallet explorer and tell us if it says that the transaction is confirmed or not.

Also share with us the fee rate you used in Sats/vbytes

It is also likely that your Binance account was just not credited and yet the transaction go confirmed a while ago. Binance changed their Bitcoin addresses a few months ago. Once you send the transaction to the old address. Nothing will reflect in your account until you carry out a manual approval. This happened to me a few weeks back.

If your node is fully synced and it only took up 13.6GB, then it's a pruned node.

Btw, you never told us how much you paid in fees (sats/vByte). Do you care to share that information or share the transaction ID of the transaction you sent to Binance? No one can steal your bitcoin if you share the transaction ID, but you are giving up your privacy by doing so. People would know your addresses.

Do you actually intend to resend or cancel the transaction?

That Bitcoin Core version that you're using has opt-in "replace-by-fee" enabled by default, so it's highly likely that you can bump the transaction fee by utilizing that feature if you only need to create a replacement transaction with higher fee rate that sends to the same recipient.
That's if you didn't disabled the option in the 'Send' tab.

To bump:
The simple method is to look for the transaction in your "Transactions" tab, right-click on it and select "Increase transaction fee".
That will create a replacement transaction with the default fee estimation.

The quite complicated method is by using the console/command line to issue bumpfee command that has more control.
In this case, you should open the console, select the correct wallet in the console's drop-down menu (only if you have multiple wallets).
Then type the command:Replace "Transaction ID" with your transaction's TXID, and fee_rate's value: "10" into your intended fee rate in sat/vB.

---

On the other hand, if you want to "cancel" it, you must wait for it to get dropped from you Bitcoin Core node's mempool.
You can check that by right-clicking on it and see if "Abandon transaction" is available (not grayed-out).
If so, you can use it to make the inputs that it's trying to spend available for your new transaction.

They are assuming that you're using an SPV wallet like Electrum that relies on a server, you don't have to do that in Bitcoin Core.
Bitcoin Core on the other hand is a full node software, it has its own mempool, blocks and UTXO set.

It's not just a low fee that makes it seem unconfirmed in Bitcoin Core.
If you want, you can share the TXID here so people can easily get to the point. That's if you're willing to show your transaction's addresses.

I am using Bitcoin Core version v27.0 zip version. No idea what's replace-by-fee until this morning. Nor what wallet I used. Previously had older version of Bitcoin Core; I read I just need to copy the wallet.dat file from my old laptop (which I did), downloaded the current Bitcoin Core version on my new desktop, drop in the wallet.dat file and ran. It looks like it's all caught up when I send out on July 4th, 2024.



Switch servers? I'm not sure what do you mean? Where do I find the server that I'm connected to?
I'm sorry - I'm not familiar with the inner workings of bitcoin. Haven't really played with it. Just got an address long time ago - played the click and get free bitcoin for a bit. That's why the amount is so tiny.



No idea whether it's pruned or full node. How do I tell? Thanks!
If I have to guess, I'd guess it's pruned. Why? Because in my old laptop, it used up quite a bit of my hard disk space. On my recent desktop, I bought extra hard disk thinking it'll be for bitcoin; but, it's used just 13.6GB - it's much much much less than when it was on my old laptop.

Yeah, I agree I didn't mention that Bitcoin core does not support RBF it is not just available on the GUI but you need to manually use a command through the console or Bitcoin-cli to bump the fee.

Let us just assume that he is using Bitcoin Core. He can make it fully sync and increase the fee on Bitcoin Core because the wallet is also supporting replace-by-fee.

If truly he is using Bitcoin Core, I think he will know the differences between full clients and SPV wallets.

I just want to confirm since you mentioned you are using Bitcoin core how did you set up your wallet on Bitcoin core is it pruned or full node? Because if it's a full node it requires you to download the whole blockchain including newly generated blocks and maybe you made a transaction while it does not fully sync if you did then the transaction is not broadcasted yet to the mainnet If I were you better switch to Electrum wallet it is way more easier to use, it doesn't requires you to download the whole blockchain and if you have stuck transaction you can bump or cancel(double-spend) the transaction.

Experienced this before, what i tried is changed my wallet since RBF is not enabled on the current wallet, good thing it was imported on different wallet, the transaction shows unconfirmed on the wallet where i send the tx but shows normal in the other wallet probably because of the difference of node server used between the so wallets. So i used the other wallet to send it again and it works.

Take note that as long as the transaction is valid, it can be confirmed. It's possible that your transaction will be confirmed even after months.
If you don't want the transaction to be confirmed for any reason, you must make a new transaction with the same input and invalidate that transaction. You can do so easily, if the transaction has been flagged as RBF.

It is not the nodes that keeps broadcasting it but rather the wallet or exchange sometimes does. What happens why it is prolonged like that is that some nodes might still have it in their mempool even after two weeks due to differences in each nodes settings. And that’s why you still see It even after you might feel it should be dropped. The thing to do is to switch servers and check for the server that doesn’t have it then you can simply broadcast a new transaction again with higher fees to replace the old one.



RBF is bumping fee method know as replaced by fee where you bump the transaction with a higher fee than the initial transaction fee. It can be to the initial address or to another new address like even the sending address, this feature isn’t available to all wallets though. That is the protocol on which the cancel transaction is made on. So if you want the unconfirmed transaction back to the sending address then you can simply pick the address during RBF or send it to any of the address on that same wallet

It is 14 days on Bitcoin Core by default for unconfirmed transactions to drop. So it should not take more than 2 weeks for the transaction to drop from mempool.

@New2024, what wallet did you use? I am asking to know if you can use replace-by-fee or not.

Thank you Mia and all for the guidance. I guess I'll patiently wait for the transaction to age out and amount return back to me.

It means replace by fee.
Check out the detailed explanation HERE

Apologies - missed your earlier point

What is RBF?