MultiBit HD 0.2.0 released - Buy/Sell bitcoin using Glidera

[jim618]

Yes that's right.

The additional complexity with HD wallets (unfortunately) is that there are two 'paths' that are used in different wallets.
These are like junctions in a city where you start creating addresses from.

It's unfortunate that there are two main standards but it is what it is.

If you have a regular MultiBit HD wallet it uses BIP32
and there is also a standard used by Trezor and others that is BIP44

If you use BIP32 wallet words in a BIP44 wallet you won't see any transactions (and vice versa).

The transaction id you sent me, when I checked, hadn't confirmed so you'll probably want to wait until that confirms (assuming it is in the same wallet)

[jim618]

https://blockchain.info/tx/a56df3201bf23fb47d99dd5276d3d93ec457a786dc3edb50ba2de1842f31e682

It's unconfirmed (as I type) due to low fees.
Thus it's change will not be confirmed and you'll see a "+Unconfirmed btc amount" appear in your header of MultiBit HD.
This is completely normal.

You'll need to wait until it confirms.

[alexfront]

jim618, How would you explain this transaction: https://blockchain.info/tx-index/547b5d1ef225ed4b1df1881018319a6577165892af25f643d8613bda8c1acb5c

It's showing confirmed on the blockchain but it's showing unconfirmed in MultiBit. Thanks

[chemodan]

alexfront, maybe the transaction has unknown status in MultiBit HD? You can see in transaction details. If it has uhknown status this is same case as mine

[alexfront]

chemodan, It does have Unknown status in Multibit so something in the program is reading it incorrectly.

[chemodan]

I have same trouble. I lost much money with it

[jim618]

jim618, How would you explain this transaction: https://blockchain.info/tx-index/547b5d1ef225ed4b1df1881018319a6577165892af25f643d8613bda8c1acb5c

It's showing confirmed on the blockchain but it's showing unconfirmed in MultiBit. Thanks

According to your posts, you have tried doing a restore of your wallet.
Restore is primarily for when you need to recover a backup (say you've lost your laptop).

There is help on pretty much all aspects of using MultiBit HD available in app.
If you have a read of:
https://multibit.org/en/help/hd0.2/repair-wallet.html

You'll see that doing a 'Tools | Repair wallet' will resync your wallet to what's on the blockchain.
Try that.

[jim618]

https://blockchain.info/tx/a56df3201bf23fb47d99dd5276d3d93ec457a786dc3edb50ba2de1842f31e682

It's unconfirmed (as I type) due to low fees.
Thus it's change will not be confirmed and you'll see a "+Unconfirmed btc amount" appear in your header of MultiBit HD.
This is completely normal.

You'll need to wait until it confirms.

@chemodan
As this transaction is now confirmed (98 blocks deep when I looked), have you tried a 'Tools | Repair wallet' to resync your wallet to the blockchain ?

[alexfront]

I have already tried a repair twice. Still no luck. I'll try it again here but I'm pretty sure this is just a problem with the new update not recognizing my transaction as received.

[alexfront]

The repair just finished and it's still unconfirmed.

[alexfront]

Is there some bug in the windows version of the update (0.2.0)? ...because both chemodan and I are using windows.

[chemodan]

Is there some bug in the windows version of the update (0.2.0)? ...because both chemodan and I are using windows.

Not only Windows. On Ubuntu same result

[chemodan]

Dear jim618, now you are aware. Wnen you and other developers fix this biggest bug? The bug appears only in 0.2.0. Also why previous versions (0.1.2 or 0.1.4) cannot connect if I install them?

[alexfront]

Good to know. Well all I know is it's definitely a software issue.

[jim618]

@alexfront About 90% of our downloads are on Windows and the code base is virtually identical so I don't think it is that.

@chemodan Please be patient. Constantly posting doesn't actually progress anything.

Most likely it is a bug as it has also been raised here:
https://github.com/bitcoin-solutions/multibit-hd/issues/862

It is most likely a combination of two separate bugs, probably:
1) Transactions losing their transaction confidence. There is an object Context which looks after these and it's been a bit problematic in the past.
2) Wallet synchronisation is probably not handling the transition Unknown -> Confirmed correctly.

The incidence rate of this bug (3 instances in about 50K usages of v0.2.0 so far) would indicate that it is a combination of circumstances.
These bugs aren't terribly easily to reproduce. Both these areas of responsibility are in the Bitcoin network management code, bitcoinj, rather than the MultiBit HD code itself.


Anyhow, there are a couple of possible workarounds:
1) You should be able to use your wallet words in BreadWallet. This is an iOS wallet only.
2) A fresh wallet recreate may avoid the 'Unknown status' problem so can someone try this:

A) Open MultiBit HD, enter your wallet password and then goto 'Manage wallet | Wallet dashboard' and write down:
    i) The application data directory
   ii) The wallet directory. This is in the format 'mbhd-11111111-22222222-33333333-44444444-55555555'
B) Close MultiBit HD
C) REALLY make sure you close MultiBit HD. It's important
D) Go into your OS's file exporer and rename the wallet directory to 'old-mbhd-<the long number>'
    What this does is makes MultiBit HD 'forget' about the wallet and transaction status
E) Open MultiBit HD and do a 'restore wallet from wallet words'. Follow the wizard and enter the wallet words for your wallet.

This should do a restore from nothing and do a clean sync with the Bitcoin network.
You'll lose your notes and exchange rates but I am hoping that all your transactions will confirm (assuming they actually ARE confirmed on the Bitcoin network).

Once someone tries this can they report back if it works as it will be a useful workaround for others.

[alexfront]

I'm trying the "fresh wallet" as you stated and I can't even get it to finish syncing. It stalls around 50%.

[jim618]

I think there is actually an attack on the Bitcoin network at the moment where someone is firing up lots of Amazon virtual machines that grab bitcoind connections. Ironically they are using both MultiBit Classic and HD to make these connections. That will leave less connections for real users.

If you find that your sync slows down to nothing then you can try restarting your MultiBit HD and it will make fresh Bitcoin network connections. That can help sometimes.

[alexfront]

The sync just finished and it did not work. My whole wallet is still showing as unconfirmed. Any other suggestions? I don't have a iphone. I may be able to use one this weekend though but I would prefer not to.

[jim618]

On the github issues database, user GreenOut tried the same technique and it worked successfully:
https://github.com/bitcoin-solutions/multibit-hd/issues/862#issuecomment-185816284

I would try and get access to an iPhone yes and use BreadWallet yes.

[alexfront]

So this is some other bug then. So you don't have any other suggestions to fix? I might not be able to use an iphone. I'm not sure.