Ahhhh ok... yeah, I see what has happened... you've created multiple "wallets" inside your b.info wallet right? That's easy enough to work around...

When you import your seed into Electrum, and select "BIP39 seed" from options... it gives a default derivation path of m/44'/0'/0' - That is for your first b.info wallet... the others will be:
- m/44'/0'/1'
- m/44'/0'/2'
- m/44'/0'/3' ... etc etc...

Electrum doesn't support multiple accounts in a single wallet... so you'll need to create a new wallet for each of the "accounts" that you have in b.info that have coins in them

Can you see all your transaction History in Electrum tho? is the balance correct?

In Electrum... on the "Addresses" tab (Wallet -> Addresses), have you expanded both the "Change" section and the "Used" sections? (click the '>' symbol so it becomes a 'V' symbol)...








In Mycelium, are your addresses all in the same "account"? or are they in different "accounts"??:


Do you get Account 1 and Account 2 etc? or only 1 HD account? If they're in different accounts, to see them all in Electrum, you need to create a different wallet for each account... when you import the BIP39 seed and it asks for an account number, 0 = MyceliumAccount1, 1 = MyceliumAccount2 etc etc


The only other reason I can think of that they don't show... would be the gap limit issue

No. They are using the same underlying technology for private/public keys... ie. ECDSA. At the moment, the only differences are the "consensus rules"... whereby BCH is allowing up to 8MB blocks... and in the transaction signing algorithm which was done to prevent "Replay Attacks"... (ie. BCC transaction is not valid on BTC chain, and BTC transaction is not valid on BCC chain)



Technically, all addresses already exist... as they're just very large numbers. Having said that, until an address is used in a transaction which is then broadcast and confirmed, there is no record of it on the blockchain.



Yes.



See #3.



So far, I have found:
Blockchair: https://blockchair.com/bitcoin-cash/blocks
Blockdozer: http://blockdozer.com/insight/

Shutdown the dicebot... Then have a look in your %AppData%\DiceBot2 directory... You should see a couple of Settings files. Backup those files and then delete (or rename) them... and then restart the Bot, it will be back to "default" settings for everything.

Given that the current block height for BTC chain is: 478,788... then either your BitcoinCore is not synced up properly... OR Armory is not talking to your Bitcoin Core properly and has not synced up it's database...

You'll need to post the db.log and armorydebug.log files (use pastebin.com and provide the links )

Did you import an Electrum seed or a BIP39 seed that was from another wallet? Electrum does not store imported BIP39 seeds in the wallet file... so it is unable to be retrieved (on desktop, the "Wallet - Seed" menu item is greyed out and not clickable... on mobile it gives "invalid pin" error)

You're using a MultiSig (or 2FA which is just MultiSig wallet shared with TrustedCoin)... MultiSig is broken in the released version of Electron Cash at the moment... But they have a fix that has been merged to the github... Refer: https://github.com/fyookball/electrum/issues/6 and https://github.com/fyookball/electrum/pull/13

You'll need to download/clone the github and run from sources to be able to use MultiSig... if you have 2FA you need to restore from 2FA seed and disable 2FA when prompted to "keep or disable"... as TrustedCoin won't sign the transaction as BCC and it will still be rejected

They've merged a patch that fixes this... refer: https://github.com/fyookball/electrum/issues/6 and https://github.com/fyookball/electrum/pull/13

The catch is that you have to run from source (or compile your own) until they've actually released a new compiled version. So, if you're desperate to get the coins out, you'll need to clone or download their repo and run that way.

Also, a 2FA wallet won't work regardless... as it requires signing by TrustedCoin... who will sign it as a BTC transaction and it will get rejected by BCC network. You'll need to restore from 2FA seed and disable 2FA when prompted to "keep or disable" 2FA.

Feel free to send them here: 16qkTAUmtCdBYfXXKKGKqD8pAYtL1T5pqV

Seriously tho, the only place I know taking BCC transactions is ViaBTC... and possibly Kraken (still waiting on my verification to be processed so I can check if the wallet is taking deposits)... Bittrex is trading, but the wallet is disabled "in maintenance", so you cannot deposit or withdraw at this time.

No... you can't just import the private keys for a MultiSig wallet, because each address has at least 2 keys required to be able to sign the transaction(s). If you import a private key, you'll end up with a "normal" '1' bitcoin address that only has 1 key... and won't actually contain any coins.

You'd probably be able to do it by crafting a MultiSig transaction manually... but honestly, you're probably better off trying to get Electron Cash with the new MultiSig patch running from sources...

Having said that, even with MultiSig patch, be aware that 2FA will still not work, because TrustedCoin will still be signing the transaction as BTC which will cause it to fail. If you have 2FA, you need to restore from seed and disable 2FA when prompted to "keep or disable"... This will restore 2 of the 3 private keys into your ElectronCash wallet so you will be able to sign the BCC transactions correctly.

Only if you have NO password set... if you set a password, all sensitive info like Seed and Master Private Key (xprv) will always be encrypted in the wallet file (even if the wallet file itself is unencrypted).

So if you restore from seed and set a new password, your seed/keys are encrypted (and so is the wallet file if you leave the "encrypt wallet file" box checked which is the default)

You'll need to extract the keys from either your .key backup... or your wallet file. I have some python scripts that will do this. 

The preferred choice would be using the wallet file and password using decrypt_multibit_classic_walletkeys.py... but if you can find a .key file, you can try decrypt_multibit_classic_keys.py as well.

Electrum is not (and probably will not be) compatible with BCC (unless ThomasV makes some updates)... BCC changed the way transactions are created/signed to prevent people losing BTC due to what is known as a "replay attack"... BTC transactions are now no longer valid on BCC network... and BCC transactions are not valid on BTC network...

To get BCC, you need to use a BCC wallet.

Yes... ThomasV updated Electrum v2.9.0... it has a feature where you can specify the derivation path for imported BIP39 seeds... so you can now import MultiBitHD seeds directly into Electrum!

Simply create a new wallet in Electrum... "Standard Wallet -> I already have a seed -> type in seed, click the "Options" Button, select "BIP39 seed" -> then when prompted, enter a derivation path of: m/0' (NOTE: that is a zero and an apostrophe... the ' is VERY important!)

There is a nice YouTube tutorial that shows the whole process here: https://www.youtube.com/watch?v=E-KcY6KUVnY

ThomasV made it so you can import MultiBitHD seeds into Electrum v2.9.0.

You create a new wallet, select I already have seed, when you type seed you need to click the "options" button and select BIP39 seed. It will ask for a derivation path... you need to use: m/0' (note the ' it is important... m/0')

That should show all your MultiBitHD addresses and history.

To get BCC, you'll need ElectronCash (www.electroncash.org) v2.9.0 it also supports this feature as it is a fork of Electrum modified to work with BCC. Suggest you do research as there are some issues with it not connecting to BCC chain sometimes. http://reddit.com/r/btc/comments/6qyn18/electroncash_notice_how_to_select_bitcoincash/

You have a 2FA wallet... which is MultiSig... MultiSig is broken in ElectronCash: https://github.com/fyookball/electrum/issues/6

A fix has been found apparently, and a patch has been madr, but you'll need to compile yourself or download and run from the sources.

However, you are using 2FA, which requires signing by TrustedCoin... as far as i know, they don't  support BCC... so any transaction you do will fail when they sign it as a BTC transaction. You need to restore your 2FA seed and "disable" 2FA when prompted so you can sign the transactions on your computer without needing TrustedCoin

Honestly, if you managed to get John The Ripper working... you should be able to follow the instructions here: https://github.com/gurnec/btcrecover/blob/master/docs/INSTALL.md to get btcrecover and the required modules like pycrypto etc installed and working.

It should be able to test passwords a lot faster than John The Ripper.

You seem to have already generated a potential password list... so you can use that with btcrecover: https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#the-passwordlist

You're going to be waiting a while then... either for someone to make another lightweight BCC wallet... or to download the blockchain using BitcoinABC.

Electron Cash can be run from sources if you're concerned about using the binaries. Just goto github (https://github.com/fyookball/electrum), download the full repo using the "clone or download" button, extract the zip and go from there...

The source is fully open and you can view/audit all the changes made since it was forked from the Electrum repo.


Given they're currently mining about 10 blocks a day... a lot smaller than the BTC chain

Be careful when copy/pasting stuff when signing messages. A stray " " (space) or "linefeed/carriage return" character at the end of the message can screw it all up. Make sure that your copied message from the Stellar Lumens site is like this (without quotes of course, just added them to make it obvious ):

"Stellar.org Bitcoin Giveaway Round 2: GBWY6GJLKSDJLKSDJWER2384320HKJH"

NOT

"Stellar.org Bitcoin Giveaway Round 2: GBWY6GJLKSDJLKSDJWER2384320HKJH "  <--- Extra space

or

"Stellar.org Bitcoin Giveaway Round 2: GBWY6GJLKSDJLKSDJWER2384320HKJH
" <--- Linefeed/carriage return

The same applies when you copy the signature back into the Stellar Lumens claim form... make sure you have ALL the characters (sometimes it will miss the "=" off the end if you try double clicking to select) and make sure that when you paste it into the form, that there isn't extra whitespace at the end.

You can skip a step... the whole point of sending BTC to a new wallet is so that when you use your seed in a BCC wallet, that if that wallet is "bad"™, only your BCC is at risk, as your BTC has already been moved to a new wallet

So in your situation, I'd do the following:

Step 1. Create a new Electrum Wallet
Step 2. Send BTC from MultiBitHD to new Electrum Wallet
Step 3. Create a new BCC Wallet (I assume you're going to use ElectronCash so you can just direct import MBHD Seed)
Step 4. Import MBHD seed into BCC Wallet

You now have BTC in an Electrum wallet (with newSeed)... and BCC in ElectronCash (with oldSeed)

NOTES: you'll only need to import MultiBitHD Seed to Electrum (and create a temp Electrum wallet) if MultiBitHD has stopped functioning properly for you ("Password can't unlock the wallet" etc)
Be careful with Electron Cash... there are fake websites distributing bad versions... the correct website is: http://www.electroncash.org/ The true website has a link to the "signatures and hashes" at the bottom, the fakes one don't. Also, there can be issues running ElectronCash on the right chain... refer here: https://www.reddit.com/r/btc/comments/6qyn18/electroncash_notice_how_to_select_bitcoincash/


ps. you won't "miss out" on BCC... that BCC will be there until someone moves it using the private keys for your MultiBitHD wallet... it isn't a race, there isn't a time limit... I'm guessing your real concern is that BCC might dump before you get a chance to sell it