Wherever you read that... it is wrong... the blockchain is currently running a little over 150Gigs... not even close to 1 TB.


Sounds like a good idea... make backup(s) of the wallet.dat file... then update to the latest version of Bitcoin Core.


If you don't have the right password, you will not be able to export your private keys... nor send funds out. To test if you have the correct password, you can use the "console" and the "walletpassphrase" command

- Help -> Debug Window -> Console
- use the command: walletpassphrase "YOUR-PASS-PHRASE" 1

If the passphrase is correct, you will get the response "null"... otherwise, you'll get an error message like "Error: The wallet passphrase entered was incorrect. (code -14)"

There must be something wrong with the way you recovered the wallet to start with... I do not understand the error about "__db.001"... nor why it is looking in the default Bitcoin datadir for this file... it shouldn't be necessary?

Given you mentioned you got some "odd" output from the --recover option about it finding 102 keys... and not the "usual" output that people get... I'm wondering if the recover process has not worked properly and the recovered_wallet.dat is invalid/broken?

It is possible, given that pywallet mentions that you are missing some libraries (ecsda, pycrypto and libssl) that this may have prevented PyWallet from functioning properly in the first place.

Try the following command:

Then try running the --recover process again and see if it outputs different info.

The problem is that your FIRST transaction: https://btc.com/eec7c8cb54bd68ad8327dcb7ce4358534306ab5a96758051812f4fa73822396e

has paid ZERO fees.   It is highly unlikely that this transaction will EVER confirm as it has not propagated well and most nodes will refuse to relay it, so a miner is unlikely to see it in the first place... let alone include it in a block with 0 fee.

Your SECOND transaction: https://btc.com/3f0725d8af325096c86aa58e7323a8f7157668840323d979b99ee0038a6ab2eb#in_0

is attempting to spend the unconfirmed output from the first... Obviously, it can never confirm until the first one does... and as mentioned previously, the first one is unlikely to ever confirm.


You should start Bitcoin Core using the "-walletbroadcast=0" from commandline (or add "walletbroadcast=0" entry in bitcoin.conf). This will prevent your wallet from attempting to rebroadcast these transactions.

Then, right click the transactions in your transaction history and select "abandon transaction"... then shut down Bitcoin Core... and restart it with "-zapwallettxes" (you can remove the -walletbroadcast=0 option at this point)

This should remove the transactions from your transaction history, so your wallet will no longer rebroadcast them. You should then be able to attempt to send out transactions using PROPER fees! refer to:
https://bitcoinfees.earn.com/
https://btc.com/stats/unconfirmed-tx

Did you even READ the article? It specifically states that the "mybtgwallet" webscamsite was responsible for the theft:

Having said that, it really shouldn't come as any surprise to anyone, that a relatively unknown website asking you to input your private keys and/or recovery seed turns out to be a scam...


Furthermore, it also mentions that the "John Dass" guy who was responsible for "mybtgwallet" was NEVER part of the BTG Development Team:

It might pay to actually READ things properly before throwing some serious scam accusations and FUD around!

The Bitcoin Gold Core wallet is opensource and, as far as I'm aware, not malicious and not involved in any theft of any crypto currency. Happy to be corrected if you have some actual proof that shows otherwise.

Pretty much... if you have moved all the BTC from those keys... you should be able to sweep the BCH from them following that process...

If they ever release a BTG compatible fork of Electrum, you'll be able to do the same thing to claim your BTG as well (assuming your BTC was still on those keys on 24th October)

Not sure if either one is "official".. but the block explorers I've found are:
https://btgexp.com/
and
https://btgexplorer.com/

you'll probably be waiting a while for a BTG "Electrum" fork.

Pass... without screenshots and/or actually seeing what the script was doing, it is hard for me to say if it was doing anything "odd"...

During one test run, I saw at one part that it had found 7 wallets... I have no idea how, there was 1 file on the USB stick! I suspect it might have been a previous copy of the file that was deleted. I don't recall seeing that information on previous runs though??!

I believe the partial recovered file, is just the private keys it has been able to find. PyWallet then attempts to build an actual wallet file using both the compressed and uncompressed addresses (and associated compressed/uncompressed WIFs) for all the private keys it has found... as it has no way of knowing which one was actually in use in your wallet file. I believe this is the reason that the partial file is smaller than the "recovered_wallet.dat"

you option is to double check with Bitpanda that your email address that they have on file is correct. If you're not getting their emails, and it's not in your spam folder, then chances are they're either sending to the wrong address because that's what they have on file... or your email system is broken.

Chances are that no one here can help you with any of this

Your only option is to attempt to troubleshoot your email system (What email provider are you using?) or the BitPanda system with the help of BitPanda support.

 the other recovered files are just temporary files that pywallet has created while searching for wallets and processing found keys etc. they're not required for anything and can be safely deleted if you want.

no idea if a pre-HD version will work. I've not tried it. I just dumped the private keys from the recovered wallet. Didn't try loading it into Core. Give it a go and see if it works.

they're slowly starting to confirm now... The earliest one (https://blockchain.info/tx/b2b2657a8f32e6796ba7945974eef0c73ec95066e68c380f05ce1f3352dcd8ab) now has no unconfirmed parents, so should confirm soon. The others with the low fees are a bit more tricky. Use the accelerators or wait

in future, you should be more careful about spending  outputs from unconfirmed transactions.

If you have access to the private keys for the Bitcoin Cash Wallet, then you can recover your Bitcoins.

What Bitcoin Cash wallet were you using? and do you have either the private keys or a "12 word seed mnemonic" backup phrase? If you don't have either of those things, recovery of your bitcoins will be near impossible.

Your bitcoins are not connected to that particular laptop... nor are they necessarily stuck in Armory. What you need is the private keys for the addresses that have your bitcoins, you can then import those private keys to the Bitcoin wallet of your choice.


Unfortunately, Armory wallet files are ONLY able to be used with Armory.

Also, 0.96 is NOT the latest version... there was a big "thing" with Armory a while back where the original developers abandoned the project for "reasons"... and the project was picked up by another developer. The best website for Armory now is: www.btcarmory.com
- The latest release is available here: https://github.com/goatpig/BitcoinArmory/releases
- Also, for Armory support try posting your queries here: https://bitcointalk.org/index.php?board=97.0

If you can get Armory open, you should be able to export your private keys from your wallet file:

- Select Wallet from list then click Wallet Properties -> Backup this wallet -> See other backup options -> Export keys list -> Click "Export Keys list" button.
- Then make sure that "Address String", "Private  key (plain Base58)", "include unused (address pool)" and "omit spaces in key data" are all checked and you can copy/paste your addresses/private keys from the text box or save it to a file etc.

I'm not even sure you CAN load the recovered .dat file into Bitcoin Core... Pywallet is quite old... and doesn't really work with newer wallet files... so I doubt that the wallet files that it generates will work with newer versions unless you upgrade the wallet file, or run Bitcoin Core in the legacy "non-HD" mode.

First, make several copies of the recovered wallet .dat, to save you having to run the pywallet --recover again if anything goes wrong.

- Then make sure that Bitcoin Core is not running
- Then put one copy of the recovered wallet .dat into the Bitcoin Core Data Directory and rename it "wallet.dat"
- Start Bitcoin Core with the -upgradewallet command

If that doesn't work... try starting Bitcoin Core with -usehd=0 command


If both of those fail, then you're going to have to try and extract the private keys from the recovered wallet dat and import them into a wallet manually.

To achieve that, your best option is to probably to use the pywallet "dumpwallet" command... with the recovered_wallet_1511377727.dat file... and just dump the whole thing out to a text file. If you give it the wallet passphrase that you selected when you did the "recovery", it will also include the private keys

To check that the command is working OK and pywallet can dump the wallet:

To dump the wallet out to a text file, with private keys encrypted (so you can check the addresses):

At this point, you should find a "walletDump-NoKeys.txt" file in "C:\Users\Catherine\Dowloads\pywallet" that you can open with a text editor... you should be able to see all the addresses that have been "recovered". I would suggest searching through these to see if you can find addresses that hold coins (input the addresses on a block explorer like www.blockchain.info).



To dump out the wallet INCLUDING your private keys to the screen ONLY:

To dump out the wallet INCLUDING your private keys to a text file:

You should find a "walletDump-withKeys.txt" in the "C:\Users\Catherine\Dowloads\pywallet" that you can open with a text editor... all your "recovered" addresses and private keys should be visible... the private keys are the ones labelled "sec".

Import the private keys, that match the addresses that have coins, into the wallet of your choice.

Sounds like you have an older version... I believe that this specific functionality was added in v2.9.x. I would highly refined that you upgrade to v2.9.3:
https://download.electrum.org/2.9.3/

Without being able to specify the derivation path, you won't be able to import your MultiBit seed correctly.

I doubt it's a "lose money" kind of bug... More likely it is just a "display" bug. All the coins and transactions exist on the blockchain. That is the "true" record. What your wallet is displaying is really just a filter and can be wrong.

If in doubt, trust the blockchain. It is, for all intents and purposes, immutable.

Do you have non ASCII characters in your wallet file name and/or the directory path to where the wallet file is stored?

Ie. Japanese/Asian characters or Cyrillic or other special characters with accents like Å or ø or ü etc

Effectively, anything that isn't A-Z or a-z or 0-9

Until the BTG Devs put out a BTG compatible Electrum fork... Your only option is to export the private keys for the addresses that have BTG from Electrum and then import them into a BTG wallet.

AFAIK, no other wallets will even import an Electrum seed as it isn't BIP39 compatible.

Even the BIP39 tool will tell you it's an invalid seed unless you modify the code to work with Electrum.

Seems the Bitcoin Core is having trouble reading a particular block from your drive... possibly a corrupted database file, or your disk might be faulty.

Delete the blocks folder from here: F:\Program Files (x86)\New folder\Bitcoin\data

And try starting Bitcoin Core again... if you get the same issue occurring, it is most likely going to be a hardware fault.

If, as you have stated, your 2FA wallet is currently fully functional (ie. you have the password and the 2FA code setup correctly in Google Authenticator)... but you do NOT have the seed, then I recommend that you move all your BTC to a completely different wallet IMMEDIATELY!!!

If ANYTHING happens to your wallet (computer crash, file deleted) or you lose access to your Google Authenticator (lost/stolen or broken phone)... your coins WILL be locked in that 2FA wallet with no chance of recovery.

Create a new Electrum wallet (Standard or 2FA)... AND WRITE THE SEED DOWN! and then send all your coins from your current 2FA wallet to the new wallet ASAP.

If you don't have the seed, then there is no way for you to recover your BCH.

To get your BCH, you need 2 of the 3 private keys that control your 2FA wallet. You have one in the 2FA wallet itself, your seed "protects" a 2nd one... and the 3rd is controlled by TrustedCoin. So, without your seed, you cannot find private key #2... so you're down to only two private keys... you have one, TrustedCoin has the other. BOTH are now required to be able to sign a transaction to move the BCH.

It *might* be possible, if you contact TrustedCoin that they will help you and co-sign a BCH transaction that you create... I believe another user managed to get this done, but I wouldn't guarantee that they will.

To create that transaction, you would need to recreate your 2FA wallet as a 2-of-3 MultiSig in ElectronCash... using the 1 xprv that you have access to, and the two xpubs that represent the two missing private keys... then create and partially sign the transaction and send it to TrustedCoin and get them to cosign it.

Why do you not have the 2FA seed? The seed is the most important thing to have safely and securely backed up for ANY seed derived wallet