Firstly, No need to start multiple threads 8 hours apart asking the same question.

Secondly, no... you can't extract Bitcoin Cash from MultiBit Classic... what you can do is export your private keys from MultiBit Classic and import them into a Bitcoin Cash compatible wallet. You can find BCH wallets listed here: https://www.bitcoincash.org/

If you want it fast and easy, I'd recommend ElectronCash... import (or sweep) your private keys and your BCH should show up...

Obviously, exporting keys should not be taken lightly... it does pose a security risk to your BTC stored on those keys. Better if you move the BTC to new wallet (NOTE: MBClassic is very old and is no longer supported) with new keys etc... and then claim your BCH.

It looks like the problem is that your local wallet has the 3 unconfirmed transactions in it's history, but the actual Litecoin network has no knowledge of these transactions.

As far as I'm aware, Coinomi doesn't have a full rescan option... so if the "refresh" isn't working, you might need to restore your wallet from seed.

Make a backup of everything first and then restore using your seed. That should force it to recreate your wallet and then rescan the various blockchains for your transactions. As these transactions don't exist anywhere on the LTC network (have you looked at transaction details and confirmed the TXIDs aren't on any litecoin block explorers?)... they should not appear after the wallet is regenerated, so your 41 ltc balance should be "restored".

Just make sure you have double (or triple) checked that you have everything safely backed up before you start

No... If Bitcoin Core is indicating that your "Datadir" is D:\Program Files\Bitcoin, then you have somehow setup the Bitcoin Core datadir in a non standard location... Note: there are TWO locations for Bitcoin Core... one is the installation folder for the application itself... this usually goes to "C:\Program Files\Bitcoin"... but I suspect you may have installed it somewhere else?

Then there is the Bitcoin Core "data" directory... this is the directory where Bitcoin Core stores your wallet and the blockchain data. By default, this is usually "C:\Users\YOURUSER\AppData\Roaming\Bitcoin"... however, you indicated that your "datadir" is set to "D:\Program Files\Bitcoin"??!?


Can you please confirm that you have a "D:\Program Files\Bitcoin" directory... and that it contains the following Folders:
blocks
chainstate
database

and that it has files like:
.lock
debug.log
fee_estimates.dat
mempool.dat
wallet.dat

There is a big difference between "need" and "want".

So, I suggest that you should either learn how to code and go add a custom fee feature (Mycelium is open source)... or maybe you need to consider a new wallet (like I did)... Users have been requesting custom fees forever... the Mycelium devs have been too busy adding in ads to the app to cover their costs after they apparently managed to spend all the "ICO" money... I wouldn't be holding my breath for a custom fee input any time soon.

This is the last message before that "helpful" person decided to intervene... What was the outcome of the the rebuild and rescan? Can you repost your armorylog.txt and dblog.txt log files so we can see whether or not things are syncing properly.

Also, confirm that you have upgraded to Armory 0.96.1 from here: https://btcarmory.com/0.96.1-release/
and that you are using Bitcoin Core 0.14.2 from here: https://bitcoin.org/en/download

Because it makes no difference. What you are suggesting will require just as many inputs when the user tries to spend the coins... like I said, it doesn't matter if you have 1 address that gets 100 payments... or you have 100 addresses that get 1 payment each.

1 address => 100x 10k sats = 100 inputs totalling 0.01 BTC in 1 address
100 addresses => 1x 10k sats each = 100 inputs totalling 0.01 BTC spread over 100 addresses

Both methods end up with 100 inputs to make a total of 0.01 BTC... if you try to send 0.01 with either method, you're going to need all 100 inputs to do so.

The point here is that you should just avoid small payments... getting a new address for each dust payment isn't going to solve the problem.

Probably because that private key only had 3.907 BCH. Unless you had all you coins in one address, one private key will NOT have all your BCH either.

What wallet did you have the 51 bitcoins in before the fork? and what addresses?  You need to make sure you have the private keys for ALL the addresses that your bitcoins are in.

Where did you send the transaction from? Was it from your ledger wallet or from another wallet? If you look up the address on a block explorer, are the funds there?

True... but is there a way with your example to split into 2 of 3 type shares? That would be really great if you could have the benefits of being able to use "normal" words instead of long hex strings, but still have the safety of 2of3... so if one share gets lost, you can still recover.

I think that would make your system ever better

1. Get 12 word seed from Mycelium
2. In Electrum... "File -> New/Restore -> Standard Wallet -> I already have a seed -> click 'Options' -> Check "BIP39 Seed" -> Enter 12 word seed from Mycelium -> Leave Derivation Path as m/44'/0'/0'/0"

Wait for Electrum to sync up... it should show your transaction history and balance pretty quickly (seconds), but your transactions will probably show as "Not Verified" until it has fully downloaded the blockheaders... might take a minute or two... if you select "Tools -> Network", you should see the "blocks" number counting up... once it reaches the height of the Blockchain, currently around 481,100 or so, it is fully synced...

NOTE: I'd probably recommend that you setup a completely new wallet in Mycelium with a new seed etc. before you send the coins back... by importing your seed to Electrum you are potentially exposing it.


Hard to say what is going to happen with transaction fees to be honest... keep an eye on this: https://blockchain.info/charts/mempool-count and https://btc.com/stats/unconfirmed-tx

When the mempool count is low (10K-15K or less), you should find that the fees come back down... in any case, as long as you use a fee that is higher than 10 sats/byte, you'll be able to use the ViaBTC TX accelerator... it can be hard to get one of the limited slots tho... and even when you do it can still take up to 12 hours for them to find a block. So you need to be aware that all your coins could be "stuck" for a while if you attempt this.

Perhaps you need to use a different wallet like Electrum? You should be able to create a new wallet in Electrum using the "Use a hardware device" option... that will import your ledger nano s wallet (public keys only of course! )

Then you can either use "Wallet -> Show Addresses" or "Wallet -> Show coins"... and from either one of the Addresses or Coins tabs, you select the one you want to include in a transaction, right click and select "spend from" for an address... or "spend" for a particular coin.

You should probably be able to do the same thing with ElectronCash for your BCH

You can't get simple, direct access to the private keys from a b.info HD wallet... but you can still find out what your private keys are by using the 12 word seed and a tool like: https://iancoleman.github.io/bip39/

You just need to know what the correct Derivation Path is... I believe b.info use: m/44'/0'/0' but I'm not 100% sure on that.

It won't be on any exchanges if it was in your ledger wallet... it'll be in your ledger wallet!

You probably just sent 0.01 to yourself... If that address is still in your list of addresses that you can sign with, and you can indeed sign a message with it... it means you have the private key.

You can't... the only way to consolidate inputs is to send them all in a transaction to yourself... so that you end up with 1 big giant input... that way, when you send future transactions, you'll be at minimum size. The problem with consolidation transaction is that you'll still end up needing to see one large transaction (and get hit with large fees)

To get around this, I'd suggest you import your Mycelium seed into a desktop version of Electrum... and then you can use manual fees to do a consolidation transaction that sends ALL your coins back to one of your Mycelium addresses with a low fee (minimum of 10.1 sats/byte)... then use ViaBTC TX Accelerator to push the transaction to get it confirmed.

You probably want to wait until the network is a little less congested tho... ViaBTC TX is very popular because fees got expensive again... and there are like 30K+ transactions unconfirmed.

You can't export private keys from MultiBitHD...

However, if you're happy to use ElectronCash to get your BCH, you can just import your MultiBitHD seed into EC... select "BIP39 Seed" from the options when importing... and then, when prompted, use a derivation path of m/0' <-- Note the apostrophe, it is important!

Now it seems the "2 blocks" and "5 blocks" values are the same in my Electrum, all others are different... Looks like it is just a quirk in the dynamic fee calculation that results in the same fee being use for a wide range of blocks as ranochigo has posited in #1

It likely happens when very large numbers of transactions are all using similar fees... as opposed to being spread across a wide range

Sounds again like the server you're connected to is either not a BCH one, or it is broken.

You can always just switch off Dynamic Fees in the "Tools -> Preferences -> Fees"... and then turn on "Edit Fees Manually". You should then be able to set up your transaction, click preview to get an idea of the transaction size and calculate your fee yourself. I've no idea what the current fees for BCH network is tho... I'd guess low, as the BCH network seems fairly underutilised.

Did you just use your own made up 12 word seed? Or did you generate one? I'm pretty sure that Bitcoinj is actually BIP39 compliant, as MultiBitHD was using BitcoinJ as it's base... and MultiBitHD was generating BIP39 seeds...

I suspect maybe your Derivation Path is wrong? Do you know what the derivation path of your BitcoinJ wallet is? I can't seem to find any documentation on it.


Because Electrum (and therefore ElectronCash, as it is a fork of Electrum) has it's own proprietary seed format that is not BIP39 compatible (the checksum calculations use different methods). This is why the "BIP39 seed" option exists. So, you can either restore from an Electrum seed or a BIP39 seed... but a made up random collection of words won't work.

Your problem is that your wallet is full of dust. The wallet is using perfectly normal fees... 264 sats/byte for "Normal" and 175 sats/byte for "Low Prio"...

Currently, because of network congestion, fees got really high again... bitcoinfees.21.co says "The fastest and cheapest transaction fee is currently 300 satoshis/byte" and https://btc.com/stats/unconfirmed-tx is saying "291 sats/byte"...

If you look, you have 10 inputs for your 0.01!!?! Your transaction is 1524 bytes... a "normal" transaction is 226 bytes... your transaction is nearly SEVEN times the size of a normal transaction...

Try to avoid collecting lots of tiny inputs and you won't have this issue in the future.

And what happens if you lose one part of it? You cannot recover the whole thing can you?

You'd be better of using "Shamir Secret Sharing" and use a 2of3 system... so you still need at least 2 of the 3 parts to be able to reconstruct... so if one part gets compromised, you're still OK... but also, if one part gets lost, you can still recover with the other two.

Example here: http://point-at-infinity.org/ssss/demo.html