Balance tranforms to Unconfirmed Transaction

[ghost]

After the update a couple days ago, my wallet balance transformed itself to an Unconfirmed Transaction.

I already try to "Repair Wallet" 5 times and reinstalled the client but it doesn't change anything. There are no open transaction and all have 50+ Confirmation.

If i try to sent a payment, it tells me that i don't have enough funds available.

The Network is fully synced and there are no outstanding blocks.

Please someone find me a solution as losing your Bitcoin's after using your wallet is very disappointing.

Best Regards.

[jim618]

This looks like the same bug as described here: https://bitcointalk.org/index.php?topic=1361928.msg13927284#msg13927284

Have a look at the message contents of the link and see if either of the workarounds work for you

[jim618]

Also, can you have a look at the transactions wizard for your unconfirmed transactions (double click on the row in 'Payments') and have a look at the Transaction status.

Does it say something like 'Seen by 10 peers', or 'Transaction status unknown' ? If so, what does it say ?

Thanks

[ghost]

Exiting the client, renaming the backup folder and "restore wallet from wallet words" seem to work. Thank you for your help @jim618.

[jim618]

That's good. That will be a useful workaround until I find a software fix.

To debug this effectively I need a wallet where the problem occurs.

Would you be willing to 'burn' (i.e. never use again) the wallet where you had a problem ? Then I can have a close look at it.

This would entail: 1) Empty your wallet of all bitcoin and never use any of those addresses again. 2) Send me, zipped, the original directory - the one you renamed to 'old-mbhd-etc-etc'. 3) Send me your wallet password and wallet words.

Obviously I would be able to see your transactions and notes so I would understand if you didn't want to. Also, if you mail me it you can assume that someone, somewhere will be snooping on your data.

I ask as it's pretty much impossible to replicate this bug otherwise though.

If you are happy to do this then send me everything to jim618@fastmail.co.uk. I'll delete it once I've investigated it. Thanks.

[ghost]

Hey,

check your inbox, i sent you all information you requested. Good Luck figuring out what the heck is going on with it.

[jim618]

Hi GreenOut. Using your wallet I just did a repair wallet and all the transactions confirmed ok:

Thus it is not reproducible on my machine

[ghost]

Well, i didn't make up this issue and maybe it's because i already fixed this wallet from another PC. I can assure you that this issue was for real and i'm sorry that i can't be of any further help.

However, if i'll have this issue again in the future, i'll contact you immediately.

[jim618]

Hi GreenOut, Oh I am sure you encountered a problem as you described. It's very difficult to track down a bug if you cannot reproduce it so the first thing any dev does is to try to reproduce it.

I've asked the other users (on the bitcointalk thread) if they would be willing to send me their wallets to see if I can make progress that way.

Thanks for your feedback

[jim618]

I have put in two probabilistic fixes for the disappearing transaction confidence information:

• In 0.13.3-alice-0.2.1-SNAPSHOT : transaction#getConfidence won't overwrite a non-Unknown confidence in the Wallet with an Unknown value from the TxConfidenceTable
• In BitcoinNetworkService : the TxConfidenceTable mempool is now only reset on a Tools | Repair wallet. It was previously also being reset on a BitcoinNetworkService#shutDown

These changes will appear in MultiBit HD v0.2.1

[Codytrill]

I'm unsure whether or not I can be of any help but you're not alone. I've had this issue today, renaming the backup folder, Roaming\MultibitHD folder and restore from wallet words helped. I don't know if it was the same issue for you but my issue started after I changed my password.

I kept a backup of my old backup and Roaming\MultibitHD folders in case of. In case you're wondering why I renamed the Roamind folder too, it's because Multibit would still offer me to restore wallets from older versions instead of creating a fresh new one with the words.

Things I had tried:

• Restoring an older version of the wallet, ''works'' but wallet unable to sync to blockchain.
• Changing back my password which obviously didn't work but anything's worth trying.
• Sending a transaction to try and ''reset'' the balance, which didn't work because of missing funds.

If I can do anything else than report to help, be sure to tell me.

[jim618]

Yes it does seem like an 'occasional' bug. When you mentioned you had this happen with a change password I tried change password in the UI a few times to see if I could reproduce it without luck.

I have put in two fixes which may help (to do with the object that manages the TransactionConfidences).

We seem to have a workaround with renaming the wallet directory and doing a restore.

[Codytrill]

Reporting again on the issue, the fix didn't exactly last very long. I tried just now to send a transaction, during which MultibitHD crashed (During the broadcasting.)

Then this happened:

Applied the fix again and restored from words, sent again another transaction:

• MultibitHD started using 50%+ of the CPU
• After 2 minutes of broadcasting, exact same issue (Balance, not crashing)
• Transaction window displayed an error, not enough funds or something
• Message on top of the screen says some bitcoins are tied with ongoing transaction
• 2 minutes later, everything back to normal, transaction went through

[jim618]

@Codytrill Your last post is actually normal MulitBit HD behaviour when it does not detect your transaction propagating across the network. When the transaction gets confirmed the balance is then available to spend.

The root cause of it is that you are only connected to 3 peers. When MultiBit HD sends a transaction it: 1) Sends it to half the peers and 2) Listens to the rest of the peers to see the transaction 'reflected back'.

When it 'hears' the transaction come back again from enough peers it believes that the transaction has propagated successfully across the Bitcoin network. It is then considered a 'good' transaction and the change in your transaction you can spend.

Because you are connected to only 3 peers it doesn't hear back from enough peers and so: 1) The change is considered unspendable until the transaction confirms. That's why you get an unconfirmed amount in the header. 2) You get a warning on the dialog which is basically saying 'Hey, that transaction I didn't see it propagate so you will have to wait a bit until it confirms before you can spend the change'.

I hope that makes sense.

[Codytrill]

What I wrote after the screenshot was just a recap of what happened. I wasn't complaining about the issue. I've used Multibit enough to notice it. I just thought I'd write down how it went after fixing the wallet again.

During the crash that happened the first time, I had 9 peers or so, also, even after waiting for a while it didn't go back to normal, thatçs why I originally made the post.

[SMH17]

This issue happened to me for the third time and unfortunately to fix the issue I have been forced to use function repair wallet many times. I have received transactions without problems I have leaved MultibitHD opened and after a couple of hours: 0 .00 BTC + All my amount unconfirmed. Something in the synchronization task is bugged and needs a fix.

[kliyer]

This appears to be the same problem described in #918 & #916

[videohoskins]

I have (inadvertantly) reproduced this same problem. I leave MultiBit HD (v 0.3.0) open/running in RAM. Also, recently and unrelated, I have developed network problems. So, while trying to sort that out, I observed that my intermittent network connection directly and strongly correlates to the MultiBit HD/Unconfirmed Balance issue.

It's as if MultiBit HD 0.3.0 should be more tolerant of a flaky connection to the Internet, relying on what it knows of the blockchain from the last time it saw it.

I understand that would open all sorts of insanity. So, maybe just show the balance with a timestamp? Then persistently retry and if the blockchain can be made current again, the timestamp would fall away, being replaced by the string "up to date" or some such...

[AKWAnalytics]

kliyer: No, it has nothing to do with KeepKey. I sent coins to my wallet from an exchange and the client is telling me that there are 13 confirmations but the balance is still unconfirmed. What is going on here?

[chris13524]

I tried repairing the wallet several times, getting the unconfirmed balance every time I tried to send coins, so I resorted to searching and came across this. I recreated the wallet with my wallet words as suggested (https://bitcointalk.org/index.php?topic=1361928.msg13927284#msg13927284), and all is good.

[walkjivefly]

Same problem happened to me. I upgraded Mulitbit HD to 0.4.1 a couple of days ago and my balance showed up as Unconfirmed. I don't run the wallet very often so it's possible the problem would have been present in the previous version and I just didn't notice it. Tools/Repair fixed the problem. My last transaction was over 20,000 blocks ago. I find it more than a little disturbing that Multibit can arbitrarily decide my balance is unconfirmed, especially when I haven't made any transactions. Time for a different wallet, I think.

[hujohnson]

I also had this issue. It resolved when I ran "repair wallet". I'm including my error.log file, if that's any help. I'm running 0.4.1 on Linux Mint.

error.log.txt

[qeioz]

@jim618 I’ve tried everything in last few days and still nothing worked. I have a lot of money blocked by this bug. I’ve been using this wallet for very long time, so it has long transaction history. Things I’ve tried:

1. wallet repair (over 20 times)
2. wallet restoration on same PC and on another PC with freshly installed differnet OS.
3. breadwallet ONLY supports 12 words key and mine is longer, so I can’t use it as well as lightroom project seems discontinued (info on github+links don’t work)
4. tried restoration using older version on another PC ( 0.3.0 after 0.4.1 on main )
5. tried on both mac and windows

During restoration process about 3% of transactions have status «Unknown transaction status» while having over 40k confirmations on blackchain, but at some point (60% progress last try) they ALL turn to same unknown status and new ones seem ok until next point and so on. By the end it’s always my whole balance is unconfirmed. Please, let me know if there is any hope to get my money restored. Is there any alternative to breadwallet that supports over 12 words long keys or any help at all would be great.

[qeioz]

I finally got it solved after 3 days of trying all suggestions I was able to find by installing 4th copy of windows on new VM and old version 0.1.0 of multibit HD. Restored wallet from seed (3-4 hours) and this time it worked for some reason.

[kliyer]

Hi @qeioz , sorry for the late response. I am glad your issue was resolved. However if you need any further assistance i would suggest you contact KeepKey Support Desk at https://keepkey.freshdesk.com/support/solutions.

[rluijk]

I did have the same bug in version 0.4.1 running on Mac 10.12.1 The Repair Wallet function solved my problem. Perhaps as a quick fix, run the repair wallet behind the scenes every now and then?

[dcrafti]

With 0.4.1 on Windows 8.1, I've tried repairing the wallet and recreating it from the wallet words, and my balance is still coming up as unconfirmed, when the last transaction was probably a year ago. I also have a flaky internet connection, but MultiBit HD's been up up to date, with 10 connections...

What's the cause, and what's a real solution? Should/can I use my wallet words to restore to a totally different wallet?

[dcrafti]

I've just installed Multibit HD 0.4.1 on a different computer, restored from wallet words, and the same issue is occurring. The internet connection is a stable 100Mb/100Mb, and there are consistently 10 peers.

[dcrafti]

My solution was to install Multibit HD 0.1.

And with how precarious it all is, with no sign that the problem is being fixed, I've cleaned out my wallet with no intent to continue using Multibit HD - "The wallet you pay to use, with critical, ongoing errors"

[steflsd]

Hi, Multibit HD 0.4.1 here. Same issue as described. Running repair and deleting wallet and recreating from seed words hasn't helped.

[vess68]

Same issue, Recreated the wallet from words, did not help. Ran repair, still the same issue. This sucks, I hate to lose my coins. Are the developers clueless?

[vess68]

I fixed my issue by downloading version 0.1.1 of Multibit HD and restoring from words. Now time to find another wallet management software and get rid if this crap MultibitHD. What wallet software do you guys use?

[steflsd]

I contacted Keepkey who were really great in supporting me. They have acknowledged the bug and are working on a fix. They provided some alternative solutions to me, of which I installed breadwallet on my iphone and used the same seed words to restore the wallet which worked for me.

[gastor]

Hi, Multibit HD 0.4.1 here. Same issue as described. All transactions became 'Unconfirmed' suddenly.

I'd renamed my wallet as suggested and restored from the backup dated December 18, 2016. All transactions AFTER December 18 were repaired but all transactions BEFORE December 18 still were Unconfirmed.

I'd renamed my wallet again and restored from my first ancient backup. This time ALL transactions are repaired during synchronization.

[gustavocoding]

I finally was able to fix the issue by downloading this wallet, then going to MultiBit HD in 'Manage Wallet' -> 'Empty Wallet' and send all funds to the new wallet. As an important last step, I erased all traces of MultiBit HD from my computer.

So far the bug hasn't happened anymore, let's hope it keeps that way, fingers crossed! 👍

[dcrafti]

It's a little sad that this supposedly closed issue is resulting in so many lost customers due to a lack of developer responsiveness.

[frankwhite97]

Hello i am an angry user of MultiBit

I started to use this wallet in 2015. Worked really good up until mid-end 2016, then the wallet started to get bugged often but i resolved it by using the "repair wallet" feature.

Now what you guys described happened to me aswell, all transactions unconfirmed and balance is locked.

Installing Multibit 0.4 on another mashine and load from wallet words didnt work. What worked was installing old MultiBit version (0.1) and restoring from wallet words.

I had 7$ in my balance and i clicked "empty wallet", guess what, this JEWS from multibit took a "5$ developer fee". REALLY PISSED OFF NOW

They make a bugged SHIT wallet and even take fucking high ass fees for it. Retards i uninstalled MultiBit forever now and i will make sure to warn other people i know from this bugged piece of crap, that has the audacity to charge huge fees lmao

GOODBYE MULTIBIT AND FUCK U!!!

[gustavocoding]

LOL

[frankwhite97]

Sorry i needed to get this out of my system! Hahaa!

[XENON3]

im with AngryGrandpa on this one. This happend to me last year with 4 Bitcoins lost in limbo and i was dumb enough to give this wallet another chance this year and it happened again. Now about 0.4 bitcoins lost in limbo. The devs need to fix this ASAP. I smell a lawsuit coming. update oh my gosh, this just keeps getting worse and worse. I followed directions to back and rename a directory., Then I was able to see my Balance, then I'm like screw this I'm transferring all my BTC to another wallet, then now the Balance is Zero and it says the Bitcoin network rejected the transaction! Now, I've basically wasted half my day dealing with this, all the while Bitcoin price has dropped $20 and continues to drop and can't do anything. DEVS, are you reading what's going on here? people are losing lots and lots of money! why are you not fixing this ASAP?

[XENON3]

remember how I said this is just getting worse and worse? Now it's been 24 hours, and everything is still f*cked up. This morning, I finally see my old balance, then I try to transfer a small amount as a test. I see a new error: The error was "Could not decrypt bytes". Then I close the wallet and re-open it, then my balance switched to unconfirmed again!

Stay clear of this wallet folks, unless you like having your funds locked away.

In this 2nd picture, im just trying to send 108mB, but in the amount column, it says 349 $USD wtf!?

[BlueRaja]

I just had the same issue. Woke up this morning and suddenly my wallet is at mB 0.00.

This issue needs to be reopened, it is not acceptable that this behavior occurs.

[XENON3]

hi, nice to hear from you their support says this is related having the fees set too low when sending. at least in their software they should bump up default fee notch, or have the fees automatically dynamically adjusted. or at least have some comments or a warning on the fees settings page. But i won't use this wallet again. I had the same scare with an older various few months ago with 4 bitcoins. That made me pretty stressed out. And I ended up losing money because I could not make some trades i needed to at a critical time when the markets were moving fast. I just wanted to give the software another chance, because I like how it's synced with the bitcoin network in real time. But having the remaining balance locked away like that, I don't like how that works... This incident cost me money too. I read in a sports betting forum, some guy had to wait 72 hours, for the transaction to post, due to low fees. So, we learned the hard way. I finally see my balance now.

On Wed, Jan 25, 2017 at 12:24 PM, BlueRaja notifications@github.com wrote:

I just had the same issue. Woke up this morning and suddenly my wallet is at mB 0.00.

This issue needs to be reopened, it is not acceptable that this behavior occurs.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/keepkey/multibit-hd/issues/862#issuecomment-275206793, or mute the thread https://github.com/notifications/unsubscribe-auth/AT13cP9MtR1p4ygRSMePr-nGAiuYICspks5rV6GHgaJpZM4Hc-aD .

[hujohnson]

Adam, I actually find your account kind of alarming, because it seems to me that the representative you spoke to might have thought: "This guy is talking about unconfirmed transactions. He's getting them because his transaction fees are too low." Which is a complete misunderstanding of the issue. I am very confused as to why an ostensibly serious company like Keepkey hasn't repaired this significant problem with their wallet.

[XENON3]

yea, a strategic oversight to avoid a bad reputation for what can be a decent wallet. as well as waste everyone time explaining or giving support. I hope they learn from this, from people crying and griping in the public forums. Somehow i still just the wallet and may use it for small transactions. I'll just crank of the fees slider.

On Wed, Jan 25, 2017 at 7:18 PM, hujohnson notifications@github.com wrote:

Adam, I actually find your account kind of alarming, because it seems to me that the representative you spoke to might have thought: "This guy is talking about unconfirmed transactions. He's getting them because his transaction fees are too low." Which is a complete misunderstanding of the issue. I am very confused as to why an ostensibly serious company like Keepkey hasn't repaired this significant problem with their wallet.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/keepkey/multibit-hd/issues/862#issuecomment-275292373, or mute the thread https://github.com/notifications/unsubscribe-auth/AT13cF1t5q9_dGZGSNxyO1PpbW8uZL7xks5rWAJ7gaJpZM4Hc-aD .

[hujohnson]

I still use the wallet but I only keep the application open for the absolute minimum amount of time. I've had issues leaving it open for 30 minutes, but less than five minutes seems to be okay so far.

[BlueRaja]

I am using the default fee. So even if what you say is true, this is still a bug in the software. (And regardless, your wallet should NEVER empty itself with no indication of why...)

[XENON3]

yea, thats whats puzzling, its not like i was trying to be stingy and crank the fees down all the way to the minimum. I have sent various sums with the wallet leaving fees at default. I have one hunch, though. Here is what happened.. I transferred BTC to MultiBit wallet, as soon as the transaction confirmed and showed in my balance, I immediately proceeded to transfer about 1/4 of my BTC to another address. Then that's when it all happened. Somehow I think, if I waited a little bit more, or past the next block time, i don't think that would have happened, but im just guessing.

On Wed, Jan 25, 2017 at 7:31 PM, BlueRaja notifications@github.com wrote:

I am using the default fee. So this is still without a doubt a bug in the software.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/keepkey/multibit-hd/issues/862#issuecomment-275293866, or mute the thread https://github.com/notifications/unsubscribe-auth/AT13cOROPIw7yFVsLb94bZdWeRvXvXYJks5rWAV7gaJpZM4Hc-aD .

[dimi86pl]

Hi Guys/Ladies, I just sign up to confirm that qeioz's solution works for me. I had several unconfirmed payment after an update of Multibit HD (which were confirmed before an update). I installed version 0.1.1 (in different location than ver. 0.4.1) and removed all backups from C:\Users*user*\AppData\Roaming\MultiBitHD then restored wallet from seed. Now wallet work on both versions like charm. Cheers!

[pmarches]

I solved this issue by deleting (or moving) the file $HOME/.MultiBitHD/mbhd-<WALLET-UUID-HERE>/mbhd.checkpoints . When missing, the file will be copied from the installation directory. I believe there is a sequence of event between the transaction dates and the release date of multibit that is causing trouble.

Too bad this issue was closed, as it is ongoing.

[jhaand]

I have unfortunately just got bitten by this problem. I already tried to repair my wallet 2 times and a lot of transactions remain in limbo. This means I can't get at at my funds.

This issue should be addressed as soon as possible and fixed.

In the mean time I will do a backup restore of my wallet and see what happens.