Mycelium uses a different derivation path (m/44'/0'/0'/0 AKA BIP44) so it doesn't work with MultiBit HD keys. I've only managed to find Breadwallet so far...

I'm going to see if I can't modify my script a little to just start searching addresses generated from a given MultiBit HD seed and use a block explorer API to check for UTXOs... stopping after 100 unused addresses. I think it would be a lot faster than someone trying to copy and paste all the private keys from the BIP39 tool... and would mean that if someone had lost their mbhd.wallet.aes file and/or could not get it synced up to date for whatever reason... they could still get a list of their addresses with funds.

That transaction seems to be dropping from a lot of mempools, I could only find it on blockcypher.com... Attempting to push the transaction on btc.com, blockr.io etc all say there is an error and that it could be either an "unsigned" transaction or a "double spend"?

The address: 1H9hQPjwfXvFcrDRbWBrRC28K3j2ATjM4F looks OK... seems to have 2 UTXOs in it... so I don't see anything untoward... maybe one of the other experts can identify what is wrong...

the raw transaction is:

As I've stated in most of those other threads, your options are:

1. If you have an Android or iOS device, install "Breadwallet", restore using your MultiBit HD seed in Breadwallet and wait for it to sync up. It should recreate your wallet with all your transaction history and coins. Note: Breadwallet is the only wallet software I've found that is compatible with MultiBit HD seeds.

2. If you can't use Breadwallet, then there is the option of using my python scripts to extract the addresses/private keys from your MultiBit HD wallet. Once you have those private keys you can import or sweep them into a new wallet (I'd suggest installing Electrum and forgetting about MultiBit HD until the devs get it fixed)...

3. Wait for the devs to fix the issue... which seems to be taking quite some time.

Option 1 is probably the fastest and easiest solution to get access to your coins.
Option 2 is more complicated and requires getting python setup and running, but it will allow you to "rescue" your coins.

If you need any help, just ask. Good luck.

Current recommended fees are:
and

You are currently competing with about 160,000+ other unconfirmed transactions

It isn't Electrum charging you these fees, it is Electrum suggesting what you will need to pay if you want your transaction confirmed in a reasonable amount of time... if you choose to send with a lower fee, expect to have a long wait.

Also, trying to tell us the "absolute" fees (especially in fiat) is meaningless... Miners look at fees based on satoshis/byte...

To illustrate, your fee could be 0.1 btc, but if your transaction was 75,000 bytes, that would translate as only 133 satoshis/byte... I could probably get a 226 byte transaction with a 0.00090400 btc fee confirmed faster... as that would be 400 sats/byte.

You mean this one right?



that is "normal"... it is a poorly named dialog, but it will come up everytime you start Electrum... it is really just the password entry screen for your wallet

Not sure why it is "hanging" after you enter your password though... is your wallet really massive or something? Do you have thousands and thousands of transactions in it? Did you set it up to put your wallet on low speed storage like a usb thumb drive or something? or maybe it is a hardware issue and your hard drive is failing?

Your original transaction: https://blockchain.info/tx/7031450f8be6b12ff76cff24f18165e93da12a22d68f191ababf50cac1a2a4ea

spends from this unconfirmed transaction: https://blockchain.info/tx/42d288280bfcbc6facc4f41e7a95a8ad78d6ce4d9726f551d31f4012d539ea9c
which spends from this unconfirmed transaction: https://blockchain.info/tx/f22097a92501bfb43ed8b470dfb28afbcbf1904c99a3c284d69c3de80a7d06e8
which spends from this unconfirmed transaction: https://blockchain.info/tx/5b01c314934387a379d51b5fea2960e6bfba22ae8b8bae72c7e84f522ce950a5
which spends from this unconfirmed transaction: https://blockchain.info/tx/c99708bcbaa4347233bb5be9ac5760ba0584ae2fe0c2fe64c4b296f9d111e80a

All of those unconfirmed transactions have a fee of 133 sats/byte... which compared with the current recommended fees of
and
are all VERY low

Until all of those previous transactions confirm, your transaction isn't going anywhere... Whomever sent this chain of transactions may be attempting double spends or scams... but most likely it is an idiot web wallet service like blockchain.info that spams out huge chains of unconfirmed transactions with ridiculously low fees.

You might want to try and submit the last transaction in the list to the ViaBTC TX Accelerator (you'll have to try and submit it as close to the beginning of every hour as you can get until you get "Acceleration succeeded" message, as they only take 100 txes per hour... and their service is getting hammered with the current network load and high fees). Once that one is confirmed, do the same for the next in the list... then the next in the list etc until they're all confirmed.

Also, given the insanely high fees at the moment, even your CPFP attempt is likely to fail, as that barely covers itself at current fee levels, nevermind the parent transaction (for the record, it works out as a combined fee of 271.638755981 sats/byte for both your transactions, not bad, just not great at current levels)

In the future, you might want to find a service or deal with people who don't spend unconfirmed transactions and use proper fees.

Because apparently no-one seems to know how to use a block explorer...

Anyway, the good news is that if you indeed sent to this address: 1ADdBfwkJRse2BibjgUAmuchBU6tr3HsP, then your ~3.428 BTC are still there. The only transaction recorded is for the 3rd August 2016 which lines up with your assertion that you:

Now, if your Electrum wallet is not showing the balance there are a couple of reasons why... First, the Electrum wallet has not synced.

Is the network indicator in the bottom right corner a "Green Light"?



If it isn't, then there is a chance you're not connected to any Electrum servers (Red Light) or it is busy syncing (the blue recycling symbol)... In any case, click it and you should get a "Network" window pop up... at the top, you can see what the current block height it is at:



If this number isn't 423467 or higher, then your copy of Electrum won't see the transaction (as that is the block that this transaction was included in).

You can also go into the console and type:
and press Enter.

If you don't get "true", then that might explain why it isn't showing.

If all that checks out, then maybe that address isn't part of this particular Electrum wallet... you can go into the console and type:
and press Enter...

if you get "true", then the address is definitely in your wallet... if you get "false"... then this wallet doesn't contain that address and that is why you can't see it. If the wallet doesn't contain that address, then perhaps you created a new wallet between August and now? You'd need to restore your old wallet using the appropriate seed to see the address and balance.

If your wallet contains the address and the network is up to date... then something REALLY strange is going on... Possibly that address was beyond the gap limit for this particular install of Electrum? So when you loaded it up, it only scanned the first 50 addresses and that address was #51 or later?

Firstly, a slight correction to your terminology. The wallet is not generating 200 "wallets"... it generates addresses/keys, but your understanding is correct... you only need the 12 words.  It is the seed (or starting point), and Electrum (or MultiBit HD) will be able to rebuild your entire wallet from just those 12 words. That is the whole point of HD (Hierarchically Deterministic) wallets.

The highly complex and mathematical explanation is here: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki

A slightly more simple explanation would be that the HD wallet system is is like an infinitely long hallway, with an infinite number of doors... behind each door is a room full of addresses/keys. Your 12 words are the "starting" point in the hallway and Electrum (or MB HD) then counts down a set number of doors from your starting point and that is the room full of keys that your wallet will use.

So, let's say your 12 word seed translates as "start at Door #120"... Electrum will then count along a fixed number of doors, say 44, and that is your door, so you get all the addresses and keys behind door #164. If you reinstall your computer and start Electrum up... you put in your seed... Electrum works out that it needs to start at Door #120, counts along 44 more doors again and you get all the same addresses and keys from behind door #164

Hopefully that makes sense...

NOTE: I don't recommend that you use MultiBit HD at the moment... it has a serious bug in it that is preventing some users from opening their wallets. If you're going to upgrade to an HD wallet, I would suggest you switch to Electrum.


Classic is no longer actively maintained or supported... but that has no bearing on your transaction times. That is most likely due to 1. relatively "low fees" used as default by Classic as it is old and 2. the current network load...

The network has been crazy for a while now, and fees have been consistently above 200 satoshi/byte... I think classic defaults to something ridiculous like 50 sat/byte (assuming a minimum sized transaction)

Gingerbread 2.3?   Yikes... that is OLD...

You'll be lucky to find any Bitcoin software that works on an OS that old... most of the Android software is only going to run on like KitKat/Lollipop or higher...

This post on stackexchange goes through a step by step process of creating and signing a raw transaction... and has a worked python example.  From memory there was an old version of "Python for Android" that I think may have worked on GB... (maybe this? https://github.com/kuri65536/python-for-android) no guarantees... I certainly haven't tested or tried it.

As an alternative strategy... have you considered setting up a Virtual Machine (using Virtual Box etc) in an encrypted container (like veracrypt), with a clean OS (preferably a linux distro) installing something like Electrum or Armory on it and then removing the network adapter from the VM setup so it is no longer online... Then use can just use the software inside the "offline" VM to sign transactions?

Best of luck...

Step 1. Switch off caps-lock...
Step 2. Remove the [bold] and [color] tags from your message  
Step 3. Get a better "faucet script" or learn how to modify the one you have to use whatever API you want/need (or pay someone to do it)
Step 4. ? ??
Step 5. Profit (or, most likely, lose all your bitcoins to faucet bots)

But think what will happen if that payment channel is between you and a "payment provider"... and that provider is being utilised by your local cafe, your local convenience store, the book shop down the street, a fast food chain that you frequently visit etc etc...

It suddenly allows you to be able to make multiple "micro" transactions without the overhead of full "on chain" transactions... you don't need to stand in the store for 4 days while you wait for your transaction to confirm due to there being 150,000 unconfirmed transactions... and you don't have to pay $5 in transaction fees to purchase your $3.50 coffee with all your faucet dust.

The provider can effectively guarantee payment and your transaction can have "insta confirmation" etc...

Granted this suddenly brings the concept of "Trusted 3rd Parties" into the mix... but a vast majority of the folks who want to use bitcoin for day to day transactions aren't going to be too worried about that... if it means their transactions get confirmed almost instantly and the fees are at an acceptable level.

Obviously, not something your hardcore anti-bank, privacy loving, bitcoin hodler is interested in... but I can certainly see the benefits for a lot of folks who want bitcoin to be like android/apple/samsung pay or debit/credit card...

I guess it all depends on your definition of "average bitcoin user"

Doesn't bother me mate... Loads of people use Alts here... It isn't against the rules (18. Having multiple accounts and account sales are allowed, but account sales are discouraged.)

Just gets a bit confusing talking to "different people" about the same thing... especially before I've had my morning coffee 

Anyway, glad you got your wallet sorted... hopefully the others are working as well...

For the record, it turns out that the "datestamp" is the result of a function that works out the number of days since the Genesis block with an appended Modulo 97 checksum... which should be the "birth date" of the wallet...

LACSTS vs. gowner0303  ummmm??

You might want to pick an account and stick with it...  or be more careful if you are trying to Multi account... #justSaying

And yes, the MultiBit HD datestamp is in the form "1234/12"... it is some proprietary format that is probably only described in the MBHD code. All it is used for is telling the application to start scanning the blockchain from a certain date/block number... so if you created a wallet last month it won't need to scan the whole blockchain looking for transactions belonging to your wallet... The idea being to speed up initial synchronisation after a restore.

Posting here because the Public Slack has been closed to new subscribers...

So I downloaded Exodus, the 64 bit Windows "installer"... and ran it... without giving me ANY choices of any description (not even a cancel install box), it popped up a box saying "Installed, you can run from the icons"... well, ummm thanks??!?   maybe I would have liked some input into that process... #strikeOne...

Then I tried running Exodus... and it comes up with a lovely red bar telling me that it can't connect to the P2P network... clicking on the "learn more" I am presented with a web page about opening up ports... seriously??? you want me to start opening ports for a closed source app that connects to a P2P network??!? #strikeTwo...

Ok, well let's at least see if their claims for being compatible with BIP44 are true... I'll just get the seed and put it into the BIP39 Tool... Oh... no... I won't... because you can't do any backup until after your first deposit??!? I don't even get to see what my 12 word wallet seed is, until I put money in?... #strikeThree... you're out.  

For the record, I did restore a 12 word seed from another wallet... and it seems to have generated the same addresses and is showing my transaction history... so I'm guessing it is using the m/44'/0'/0'/0 derivation path like Mycelium... but I still can't use the backup as I haven't made a deposit??? Which apparently means that I can't add a password to the wallet?? So, now my restored wallet is just sitting there without a password to protect it??!?   

It also shows me the first address in the wallet, as opposed to the first "unused" address when I click receive after doing a restore.

And finally, when you uninstall the app... there are no notifications or anything... and it leaves behind all your data in the %appdata% directory... including your wallet, which I presume is not password protected or encrypted if you haven't successfully managed to run the backup process...

What wallet are you using that doesn't have a "Total Balance" feature showing you how many bitcoins are currently controlled by private keys in that wallet?

Or are you talking about an address? Looks something like: 19zvkoJS3k45pRi56Pt6uuTCQkCWNYuKWp or 32qmHtM33MXsMkusSk2k3rRapTt9EviPb9

If that is what you have for "wallet-nr"... then go to any block explorer like blockchain.info or blockr.io or blockcypher.com and put your address into the search box.

As I have explained in several other threads... it isn't that your password has been change or stopped working... it is just a "bad" error message being output by the application.

The easiest recovery is to simply install breadwallet on an Android or iOS device, restore using your MultiBit HD seed and you should have full access to all the funds that were in your MultiBit HD wallet.

Alternatively, if you use my python scripts... specifically the find_unspent_multibitHD_txes.py script, you will get:

1. a list of the UTXOs in your MultiBit HD wallet, along with a list of the matching Addresses/Private Key(s) for these UTXOs
2. a plain text output of your wallet (parsed_wallet.txt) NOTE: all seeds/private keys are still encrypted in this file.

My investigation into the source of this issue leads me to believe that newer transactions are unable to be parsed correctly by the wallet. This manifests as a "Transaction did not deserialise completely" message in the application debug logfile. Unfortunately, the wallet does not handle this error properly and returns with the "Password did not unlock the wallet" error

If you need any help, PM me...

ONE of your transactions is confirmed... 6071f91358893abbcaba092f47bfdc2326391fe471bd2d7e4d04b27a72ba0e94

but the other one: c2a65b68c32004c2747cedd8d33ef1830748b46953eb7a311dfe15c697c08cc3 is still unconfirmed...

Might explain why you are still missing some of the coins...

I really wish that were the case... but quite simply, it isn't...

https://bitcointalk.org/index.php?topic=1000544.0

Have a look at the mnemonic compatibility tab of the spreadsheet... the compatibility between clients is pretty limited, especially if the seed was originally from MultiBit HD... If that is true, then the only other compatible wallet currently, is Breadwallet (which is Android/iOS only)

The betting speed of the bot is limited by the site itself and how they do their API request processing... Some sites give priority to "larger" bets... I know that with crypto-games.net, bets above 1000 sats get priority... so if you're minbetting, it goes a lot slower.

But then I can bet on a different site (DuckDice) with like 10 sats... and it goes just as fast... so maybe try a different site

The "3572/18" part looks like a datestamp that you get from MultiBit HD... It also allows creation of 12, 18 or 24 word seeds.

I'd suggest you try restoring these seeds in MultiBit HD and see if they work.

Good Luck.