Thanks for the heads-up... Delayed flights are such a nuisance

You're pretty much there...

Bitcoin Install dir is where you installed the Bitcoin Core application files to, so that looks correct.
The Bitcoin Home dir is actually where the wallet.dat and blocks folder is, so in your case, it would be the "D:\Bitcoin Wallet\Data" directory

Note: it will likely say "offline" when you initially start it up until it has built the database and scanned for transactions... This can take quite a long time.

It isn't the wallet... It is the Bitcoin network.

It is full of unconfirmed transactions again... So recommended fees have increased to 450-500+ sats/byte... https://bitcoinfees.21.co

This means that even a basic transaction that only has 1 input and 1 output+1 change address (226 bytes) will need a fee of over 100,000 sats to be mined in a reasonable time.

If your fee was close to 0.025 then chances are you were using a LOT of inputs (received a lot of small payments?) Which would make your transaction size larger which results in larger fees.

You can switch off dynamic fees and set the fee manually, but then you run the risk of your transaction getting stuck due to low fee.

It's quite likely that any other wallet would probably have charged something similar (or used a low fee and your transaction might not get confirmed for hours/days)

So you have MultiBit Classic wallet file... And you know the wallet password right?

If you have MBC wallet file and password you can use my python scripts to extract the private keys: https://github.com/HardCorePawn/multibit_recovery

You want to use the "decrypt_multibit_classic_walletkeys.py" script

If Core isn't synced up to at least block#477,908 (The block the transaction was in), then it cannot show in Armory.

Armory reads the blocks from Bitcoin Core, scanning them for transactions that affect addresses in your wallet... If the block that your transaction is in doesn't exist on your disk yet, Armory can't read/scan it... So it can't show the transaction

Once core syncs last block 477908, Armory should show you the transaction.

If you're getting "invalid phrase" then chances are that it isn't a BIP39 compatible mnemonic...

Try using an offline version of: https://iancoleman.github.io/bip39/

If it also says "invalid" then you can be sure it isn't BIP39 seed... In which case, I'd guess that it was an Electrum mnemonic, as Electrum uses a slightly different method to generate/calculate mnemonic checksums to the BIP39 specification (even though it uses the same word list)...

Download Electrum, when setting up a new wallet select "I already have a seed" and try entering your 12 word mnemonic

Most likely this is a result of a combination of the current "average" fees being very high (450+ sats/byte!!?! ) and the fact that your $10 (0.0025 btc) is possibly made up of more than one input...

With recommended fees being that high, each input will require 66,600 sats (148 bytes per input * 450 sats/byte) as a fee (minus another 19000ish in fixed fees for output etc) You only have 250,000 sats to start with... So even if you had just 1 input, the max you could spend using recommended fees is less than 164,400.

If you had 2 inputs, you max spend would be 97,800 sats... 3 inputs = 31,200... Etc

Your options are:
- Turn off dynamic fees and set a low fee manually and accept the long wait time/possible stuck transaction
- wait until fees drop

The --recov_device argument should be just the drive letter... You need to give it a "device”... Not a file. If you read the stack exchange link from earlier, you'll see the user is a small USB thumb drive, put the wallet file on that and then used pywallet.

And --recov_size should be the size of that device you're scanning.

So if you had a 4gig USB thumb drive, mounted as drive G: you would use:

pywallet.py --recover --recov_device=G: --recov_size=4Gio --recov_outputdir=C:\pywallet-master\recover

Sounds like it didn't propagate well.  You can try broadcasting using:
https://blockchain.info/pushtx
http://blockr.io/tx/push
https://pool.viabtc.com/tools/BTC/broadcast/
https://live.blockcypher.com/btc/pushtx/

and see if they give any errors...

Was the private key in WIF format and does it start with a "5", a "K" or an "L"?

I vaguely remember reading that importing into b.info did weird things where it was automatically converting uncompressed and compressed addresses for imported keys. If you put your private key into an offline version of BitAddress.org (wallet details tab) do you see both the address from b.info AND the address from Electrum?

Sounds likely that you downloaded and ran the "standalone" executable... which one did you download from here: https://electrum.org/#download ?

If you just re-download the "windows installer" (https://download.electrum.org/2.9.3/electrum-2.9.3-setup.exe) and run that... it should go through a proper install and setup process and add Start menu items etc. NOTE: this will NOT overwrite your wallet etc but make sure you have the 12 word seed backed up!

You should then be able to start up Electrum and it will automatically use your current wallet

There are three levels of wallet security in Electrum:

1. No password
2. Password (No wallet file encryption)
3. Password + wallet file encryption

Level 1, your wallet file will be stored in plaintext and the keys/seed etc will be in plaintext. When you start the app, your wallet will open automatically and all balances/transactions/addresses are visible and actions can be completed without a prompt.

Level 2, your wallet file will be stored in plaintext, but private keys and seeds are stored encrypted. When you start the app, your wallet will open automatically and all balances/transactions/addresses are visible. Sensitive actions like sending transactions, viewing seed/private keys or signing messages will prompt for the password.

Level 3, your wallet file is totally encrypted and not human readable. When you start the app, you are prompted for password before wallet file can be opened and information displayed. Sensitive actions like sending transactions, viewing seed/private keys or signing messages will prompt for the password.



Sounds like you want level 3... so add a password to your wallet and make sure the "encrypt wallet file" box is ticked

note: there is only one password

By default, Electrum and ElectronCash both show milli units. You need to go into the settings and change from mBCC to BCC... that is why the numbers are all messed up.

Then just use the seed

You sent BTC from b.info to ledger... you didn't send BCH... BTC transactions do not have any effect of BCH network since the fork occurred.

All your BCH will still be sitting on the addresses/private keys from your b.info wallet. If you look at blockchair.com or blockdozer.com and look at  your old addresses, you should see your BCH balance.

If it is a new HD b.info wallet with the 12 word seed, you can import the seed mnemonic into ElectronCash and access your BCH.

good to hear you got it sorted. It's s useful set of tools, but they don't really explain some of the stuff, like needing to ensure you have actually left some coin for the transaction fee!

How do you know it was sent to a BCH address? Did you send it to a BCH address that you own? If so, you already have the private key, as private keys for BTC and BCH are the same.

Just take the private key from the BCH address and import or sweep it into a BTC wallet

You need ElectronCash for BCH... The official website is: www.electroncash.org

They also have downloads for MacOS

No drama... Glad you got it all sorted

I only asked because I've had issues on MacOS before where it installed from an external device but as soon as I ejected the device, it "disappeared"

Other than that, no idea why it might of vanished... Did you just try reinstalling? Backup you wallet file to be safe, but it shouldn't overwrite it

Did you download and run it off an external drive or USB drive?