Topic: used old multibit client, probably low fee, change stuck since 4 days (Read 601 times)

You are one of the rare ones that post their problem super-clearly and ask nicely for help.
I'm glad it's all good and I could help
I wrote you a long mail about importing into Electrum, I hope I wrote the steps good enough.

thank you so very much, issue is solved!
i'll donate both to you and to the accelerator! Saved my day !!


cheers

It doesn't matter which software you use. You have quite a number of transactions started....
While the first transaction is not confirmed, the others will wait, because they'll use the change that has to return to your wallet after the first transaction.

What to do?
https://www.viabtc.com/tools/txaccelerator/   is free, I tried to accelerate your first transaction with this, let's see what happens in the next few hours.
https://pushtx.btc.com/ is not free, but I never used it before.

Good luck!

PS. It doesn't matter if your wallet runs or not, or if you change your wallet meanwhile. I suggest you export your private key from multibit classic and move to electrum. You'll find on bitcointalk (you have to search though) tutorial how to set it to be able to adjust the fee/kb before each transaction. Check https://btc.com/stats/unconfirmed-tx or similar sites before sending ont transactions next times.

PS2. And it's confirmed! Doing now the same for the next transactions.

Bitcoin Client Software and Version Number:  Multibit (classic, old version, then 0.5.19)
Operating System: windows 10 64Bit
System Hardware Specs: Intel XEON
Description of Problem: used old multibit client, probably low fee, change stuck since 4 days
Any Related Addresses: (redacted)
Any Related Transaction IDs: (redacted)


https://blockchain.info/de/unspent?active=(redacted)v&format=html

I transfered 0.71 BTC to a different wallet, from an old system which happened to run an old version of multibit (older than the label 'classic' i suppose).
I guess the automatically chosen fee was too low, to the transfer took long. (around 3 days). The problem now is, the wallet tells the full amount it holds
can not be spent. I think the 'change transfer' (is that correct phrased?) is still 'stuck', possibly also because of the low fee. I read many tips how to fix
such an issue, and i think it will not happen again in the future again. (first of all, i installed the latest versions of Multibit HD and also restored the wallet
on a different system into multibit classic 0.5.19). To my understanding, i have to stick to that old client until the change transaction got confirmed aswell,
then i could transfer it to a current client (which features RBF, for example, which i can not use with that old client if i got it right).
So, anything i can do to ensure the client gets its change confirmed ? Maybe shutting it down for a few days so it won't retransmit it again and again, and
wait for 'the mempool to be purged' ? (sorry if this sounds like a mess!)

Help would be very apreciated and gladly rewarded with some mBTC!

Thanks a lot!