There, fixed that for you

Well that transaction is currently showing on blockchain.info and also on BlockCypher (and is in the mempool on my full node)... so it would appear that something is rebroadcasting that transaction... as BlockCypher says they received it like 8 minutes ago

If you want that transaction to go through... just hammer away at the ViaBTC TX accelerator... others have suggested to start trying to submit it at xx:55, xx:56, xx:57, xx:58, xx:59, xy:00, xy:01, xy:02, xy:03, xy:04 and xy:05 etc... as the hourly reset for the 100 tx limit may occur slightly before or after the actual hour rolls over.

If the sweep Transaction ID is not showing anywhere... then the transaction got dropped... maybe try again? Or instead of sweeping, you can just import the keys to a new wallet and then send them from there to your seeded wallet (effectively the same as sweeping)

The seed is the "starting point" for creating addresses/private keys... it is the private keys that control the coins. The idea being that as long as you have the seed, you can regenerate the same addresses/keys should your wallet be lost/destroyed/corrupted (older non-HD wallets just randomly created addresses/keys so if you lost your wallet, you couldn't recover addresses generated after last backup), so you can get access to your coins (via the private keys)

Anyway, the problem is that wallets can use different "derivation paths" from one another... which means that the addresses/keys being generated from a seed will differ.

Think of it like a long hallway which has a large number of doors labelled: 1, 2, 3, 4, 5 etc. and behind each door is a room with a large number of addresses/keys, all different from the addresses/keys in other rooms... The long hallway is your "seed"... the doors are the "derivation path"...

MultiBit HD is using Door #1... and so you get all the keys from Room #1.... however, Electrum (when importing BIP39 seeds) uses Door #44... and will give you all the addresses/keys from Room #44...

For the record, the actual derivation paths are m/0'/0 for MultiBit HD... and m/44'/0'/0'/0 for Electrum... You can play around with this website to get an idea of how changing the path changes the addresses: https://iancoleman.github.io/bip39/ (IMPORTANT: use an offline copy!!)

The "estimated BTC transacted" value in blockchain.info explorer, is just their "best guess" at how much BTC was actually sent from PersonA to PersonB, based purely on the output amounts and some weird algorithm that blockinfo has come up with... in a lot of cases, like this one... it is wrong

As mocacinno stated, in that transaction there is 1 input and 2 outputs... and blockchain.info thinks that PersonA (The exchange) sent 0.02251155 BTC to PersonB (You)... and the rest of the input was returned to PersonA's change address. However, based on what you've pasted... you actually got the 0.36701145 BTC...

Now the reason the input to the transaction was 0.390023 BTC when you only wanted 0.37028862 BTC is that this is just the way bitcoins works... you have to spend UTXOs completely... so the exchange just picked a UTXO that was in their wallet that was larger than your request + miner fee and used that to create the transaction, then they got the difference back as change.

Generally speaking, the input amount can (and often does) bear very little resemblance to any amount you are supposed to receive... Especially from organisations dealing in large volumes like exchanges. They could easily have used an input of 10 BTC... you'd still get your 0.36701145 BTC and they'd get their change...

Electrum and MultiBit HD use different Mnemonic systems (and different derivation paths if you try to restore a BIP39 seed into Electrum).

There is no way that these wallets will be in sync... ever... they'll be generating different keys/addresses from the seed.

The only wallet software that is currently compatible with MultiBit HD seed is Breadwallet (Android or iOS app)

For all intents and purposes... Yes.

The odds of someone 'randomly' generating the private key to that address is so small that you can effectively consider them lost forever. There is a chance that if quantum computing ever becomes reality that it might be possible to crack it, but I wouldn't hold my breath if I was you.

This scenario is precisely why HD wallets were developed... all addresses/keys can be recovered from the single seed... and generally, any backup will then be able to recreate any missing addresses/keys that were used after the backup was made.


There is no point... the addresses containing the "Big Payments" were created AFTER the backup was made... so now that he has restored from the backup, those addresses are effectively lost...

Electrum does indeed use it's own mnemonic scheme that is pretty much incompatible with everything

However, Electrum will allow you to import a BIP39 Seed (if you select it from the Options during seed input)... But it will only generate the correct addresses if the wallet you are importing from uses a m/44'/0'/0'/0 type (aka BIP44) derivation path (like Mycelium). This means that Electrum will happily accept the MultiBit HD seed if you try and restore... but the addresses and keys will be different because MultiBit HD uses m/0'/0

The only wallet I know of that will properly import MultiBit HD seed (now that Hive is no longer operational) is Breadwallet... which is only on Android or iOS.

To switch from MultiBit HD to Electrum, just do what Kolloh originally suggested, create a new Electrum wallet and then send all your coins from MultiBit HD to Electrum.

I believe he is talking about the situation where after sending 4 transactions, you get:

ChangeAddressA = 0.0001 btc
ChangeAddressB = 0.0002 btc
ChangeAddressC = 0.00015 btc
ChangeAddressD = 0.0003 btc

You have no other unspent outputs in your wallet... and you go to send out all your balance... ie. 0.00075 btc... but your wallet now has to use 4 inputs to do this, which jacks the transaction size up to 600 bytes... and suddenly you need to pay 132,000 sat fee, instead of 45,000 sat fee.

To the OP, at the end of the day... it makes no difference in terms of fees or transaction size, whether you use change addresses or not. If you don't use change addresses... instead of the situation outlined above, you'd just have four inputs in one address like so:

Address1 = 0.0001 btc
Address1 = 0.0002 btc
Address1 = 0.00015 btc
Address1 = 0.0003 btc

So you would still incur the penalty of having to use 4 inputs (and associated higher fees)...

Hopefully, if you have a "smart" wallet it will use the least number of unspent outputs to make up the amount you want to send... rather than just starting at the beginning of the list of unspent transactions and adding inputs until it reaches the required amount.

One trick that can be used to minimise the amount of "change dust" that you generate would be to do batch transactions using Electrum's "Pay to Many" feature...

Looks like it all got confirmed, so yay.

As for not being able to get into MultiBit HD, that seems to be a fairly common issue at the moment. Your options are:

1. If you have an Android or iOS device, import your backup seed into breadwallet. (Currently the only known wallet software that supports the m/0'/0 and m/0'/1 BIP32 derivation path that MultiBit HD uses)

or

2. You can attempt to use my python scripts that will extract the addresses/private keys that still contain unspent outputs from your MultiBit HD wallet file. You can then import or sweep these private keys into the wallet of your choice. (Recommended to sweep).

- Option 1 will mean you can still access coins sent to any of your old addresses.
- Option 2 means you will effectively have to abandon your MultiBit HD wallet and all the addresses it used.

If the phone is rooted... you should be able to use a root file explorer or terminal emulator... Most app data stuff is stored in /data/data/<APP PACKAGE>

And it looks like all the Jaxx stuff ends up in /data/data/com.kryptokit.jaxx

Unfortunately, I just did a quick check using Android on VirtualBox, and it looks like all the folders gets automatically deleted if you uninstall the app... if you don't have the wallet words, or a nandroid backup of your device from when you had Jaxx installed, chances are that your wallet (and coins) are gone

If you have Android or iOS device you can install breadwallet and import your MultiBit HD seed there.

Otherwise, you can use my python scripts to identify which private keys in your MultiBit HD wallet contain unspent outputs. You can then sweep those keys into another wallet like Electrum or Bitcoin Core etc.

I can confirm that this is indeed correct.

I just created a 2nd account in Mycelium... then created a new wallet in Electrum, set the Options on the Seed input to "BIP39" and used the Mycelium seed... then on the BIP44 Account dialog, changed the 0 to a 1... and it created the same addresses as generated by 2nd account in Mycelium.

So it would appear you can indeed import multi-account Mycelium wallets into Electrum... you just have to split them all out in to separate Electrum wallets... a bit of a nuisance, but better than nothing!

If you were using MultiBit HD, and restored with seed words... then MultiBit HD should have restored all your addresses and transactions (assuming the addresses involved were within the "gap limit" of unused addresses.

If you were using MultiBit Classic, then I am afraid that you have probably lost your coins. I've just done some tests and it seems that Classic is just creating 'random' addresses/keys...

For the record, I tested it by backing up the wallet, then I created 5 new addresses and noted them down, then I deleted the wallet files... Finally, I restored from the backup file and created new addresses and they were different from the previous ones.

I believe that it is the version of the bitcoinj library that MultiBit HD is currently using... I think it may be a little outdated and so when it receives a transaction that has had the "version" field included in the transaction hash calculation, multibit calculates a different hash (as it isn't including the version field)... and it throws out an error thinking that it wasn't able to decode the transaction properly.


You cannot use the multibit seed in Electrum or Mycelium... as stated, the ONLY wallet I've found that uses the same Derivation Path is breadwallet... reference: https://bitcointalk.org/index.php?topic=1000544.msg10862297#msg10862297 (Note: click the "mnemonic-compatible" tab on the spreadsheet... and it is MultiBit HD (standard wallet)...

if breadwallet is not an option, then you would have to use the scripts to extracts the keys...

Just to clarify "sweeping" tries to create a transaction that attempts to send all the coins from the given private key(s) into your new seed based Electrum wallet...

So you managed to get the private key out of your MultiBit HD wallet? and you attempted to sweep the coins from this private key to your new Electrum wallet... correct? Given how overloaded the mempool still is, I'm assuming it will just be unconfirmed... Can you please post the transaction IDs so we can investigate properly?

Also, you might want to check your transaction ID on a different block explorer like http://blockr.io/ or https://live.blockcypher.com/

That doesn't really solve anything though does it?

how are you supposed to get access to all your coins if you don't let the wallet sync? Sure you'll be in the wallet before it finishes syncing, but after it finishes syncing in the background after you've unlocked it, the "broken" transaction that causes the error in the first place will be back in your wallet... so the next time to restart multibit you'll get the same error...

Honestly, you are better off moving to another wallet until the MultiBit HD devs fix this issue...

Bear in mind, that without the Transaction IDs it is really hard to tell what is happening... I'm really just guessing.

Usually, it would only take 48-72 hours for your transaction to start dropping from the mempool... which would result in the bitcoins being able to be resent. However, if your transactions are still showing up on block explorers it suggests that something is rebroadcasting your transaction at regular intervals. This could be caused by your wallet... but I'm not sure if MB Classic rebroadcasts... I know Bitcoin Core does.

As for how long it would take to get confirmed... delays are at an all time high due to the massive number of transactions. It is the new "norm" for low fee transactions to take days and days... 

Firstly, congrats on being a rare specimen that actually learns from previous issues! Good to see you're being proactive regarding your fees!

However, data size of the inbound transaction does not automatically translate 1:1 with data size of an outbound transaction. So even though your inbound transaction was 2437 bytes, it may be that all the coins were placed into one output.

So, when you go to spend that output, your data size will be significantly reduced... possibly as low as 1x Input 148 bytes + 1x Output 34 bytes + Fixed 10 bytes = 192 bytes, or maybe 226 bytes if there is a 2nd output for any change.

Without being able to see the original transaction, it is a little difficult to tell, but if the original 2437 byte transaction resulted in all the coins going into one address, chances are, your new transaction will only be around 192-226 bytes, so calculate your fee accordingly.

On a side note, does blockchain.info allow you to modify the fees? Most users seem to claim that the reason they sent transactions with low 50 sat/byte type fees is because "Blockchain.info doesn't allow me to set the fee"

you probably need to type

"Python btcrecover.py --wallet NAME.dat --passwordlist NAME.txt --typos-map NAME.txt --autosave NAME.txt"

Fairly sure it needs the full name of the python script file... also, I assume you are actually using the filenames of your wallet and text files like "wallet.dat" and "myPasswordList.txt" and not just typing NAME.txt??

a "bit low"? ummm try "extremely low"

Your transaction: "Fee per byte 22.92 sat/B"

whereas the current recommended removes are more than 10x what you used:

Pay low fees, get low service...

First of all, try and calm down... I realise it is stressful having sums of money that appear to have vanished into a void and that typing in CAPS is a way to relieve stress, but it is horrible to read and to a lot of people, it looks like you're shouting.

Some things to note:

1. Resetting your MultiBit is not going to achieve anything, so don't bother.
2. You will need to provide the Transaction IDs if you want us to check your transactions out to see if there is anything untoward happening.
3. The bitcoin network is under a really heavy load right now. There are around 150,000+ unconfirmed transactions, so you are definitely not alone.

Given that we can't see your transaction, here is some general advice:

- Read this thread about "stuck transactions". It has some helpful tips.
- Keep trying with the ViaBTC TX Accelerator. Due to the huge network load, the accelerator is very popular and they only accept 100 txes per hour. They reset the counter at the start of the hour, so you have to try and time it right to get in before the 100 tx limit is reached!
- You can try and use the paid TX accelerator. Unfortunately, the only payment method at the moment appears to be Alipay which I think may be limited to China only
- You can try and contact the users Quickseller or macbook-air. However, given the large number of people who are having issues with low fee transactions getting stuck, I am sure their inboxes are crammed with people having the same problem as you.

Finally, your funds will be OK. Either your transactions will confirm (YAY!) or they won't and your funds will be respendable by your wallet... also, MultiBit Classic is longer maintained, developed or supported, you should really consider upgrading to a newer wallet (I DON'T recommend MultiBit HD, it has some bad bugs at the moment... go for Electrum).