After I downloaded a file reader that doesn’t support .dat files, my backups of my Bitcoin Core wallet are now in VCD Video File format...please help.
I’m not sure how to get rid of this problem now that I have installed this file reader app on windows 10, but any advice would be great as to how I can get the files back to .dat format. Also, one thing I noticed is that when I save the file to the usb drive, the format is in .dat format but then it automatically converts it to this other format.
If I backup my wallet.dat can I reinstall bitcoin QT without losing BTC?
Trying to get a payment. Bitcoin QT stuck synchronizing. Last block data is from 302 days ago. Any tips welcome. [UPDATE] WHAT I DID TO SOLVE THIS PROBLEM, KIND OF, AKA, A WORKAROUND. Backstory: This was also my first bitcoin transaction ever. & I'm not even mildly a computer genius. 1 Backed up my wallet.dat to a file on my desktop so I didn't lose it. (I was fucking scared of losing it) 2 Uploaded wallet.dat to : https://blockchain.info/wallet/ --- (since this was my first transaction, it's not like I had a lot of coins in my wallet so I figured I'll upload it here, cash in what I will, and move the rest someplace more secure) 3 Made a coinbase account. 4 Linked it to bank account with instant verification. (pretty neat) 5 Copied generated on coinbase (they don't explain it but coinbase is also sort of a 'wallet') 6 Pasted that address into the field on the page for sending coins on the Blockchain Wallet Page. Hit send. HELD BREATH CUZ I SENT A BUNCH OF MONEY THROUGH SPACE. The computer made a weird noise, like a DOS-y sort of beep. 7 Refreshed my Coinbase wallet and TA-DAA, they were there!!! 8 Waited while the transaction was 'pending' for a little under hour. (This is normal) 9 Sent to bank account. =] =] =]
(1) Is it true that encrypting an *existing* bitcoin-qt wallet.dat file will "invalidate" any existing backups? (2) Can I use unicode characters - eg ♥ - in the bitcoin-qt wallet passphrase?
I have an existing bitcoin-qt wallet.dat file which I want to encrypt - using the command in the bitcoin-qt Settings menu, involving creating a passphrase. I have 2 (possibly somewhat related) questions: TL;DR (1) If you encrypt an existing wallet.dat file, will the backups of the old wallet.dat file still work? (2) Can you include unicode characters - eg ♥ - in the passphrase used to encrypt a bitcoin-qt wallet.dat file? Worst-case scenario: The answers to (1) and (2) are both "no" - and I attempt to encrypt an existing wallet using unicode, and my backups no longer work (due to a new pool of addresses somehow being created?) and the passphrase isn't what I think it is (due to the unicode characters somehow being misinterpreted?) - and then I could lose all my coins?? Details (1) The following (old, short) thread claims that after you encrypt an existing wallet, any previous backups of that wallet will no longer work: https://pay.reddit.com/Bitcoin/comments/1ccfdk/encrypting_walletdat_in_bitcoinqt/ Obviously, the the first response in that thread was slightly wrong, for saying that the "server" creates a new pool of 100 addresses to draw on. So using word "server" here was certainly incorrect - but maybe the gist of what they were saying might still be correct? (if you simply change "server" to "client"). I can actually understand that there might be reasons why encrypting a wallet.dat file could cause a new pool of 100 addresses to be generated. But it does not make sense to me that this would make any older (unencrypted) backups instantly useless. It seems to me that these older, unencrypted backups would still have their private keys intact, and could thus be used in certain (perhaps limited?) ways - such as:
"sweeping" the funds from the private keys of the old, unencrypted wallet into another wallet, or
doing a normal "spend" from the private keys of the old, unencrypted wallet (However, if the old unencrypted and the new encrypted wallets now contain different pools of addresses, then I imagine that this spend would invalidate the new, encrypted wallet - because any change from the spend would be sent to a "change address" from among those in the old, unencrypted wallet - and so this amount of change would be missing from the new encrypted wallet, right?).
(2) It seems that including a few unicode characters in the bitcoin-qt wallet passphrase would make it a lot stronger (since unicode is a much larger set of characters than ascii), so I would like to include a few. But it would be more reassuring if it could be explicitly stated that this is indeed supported. Possible catastrophic interaction between (1) and (2)? If the answers to (1) and (2) were both "no" (ie, if you encrypt an existing bitcoin-qt wallet.dat file then any existing backups will not work, and unicode characters do not work in bitcoin-qt passphrases), then I'm worried there could be some kind of catastrophic interaction between (1) and (2) where I lose all my coins, as follows: (1) I encrypt my existing wallet - making my old, unencrypted wallet.dat file now invalidated (due to something involving a new pool of addresses being generated?) and (2) I use a passphrase which includes unicode characters which bitcoin-qt appears to accept at the time of creation, but which doesn't work at the time of trying to decrypt the wallet.dat file (due to something going wring with how the supposed unicode characters are actually interpreted while being entered or copied-and-pasted?). In this possible worst-case scenario, my old backups of wallet.dat no longer work, and my newly encrypted wallet.dat has some password which I'm not able to correctly enter anymore. Sorry to be so paranoid about this! Other remarks: (a) I did do a (limited) test of unicode capability for bitcoin-qt wallet.dat passphrases: simply by creating a new (empty) wallet.dat file, and creating a passphrase for it involving unicode characters, and then attempting to change the passphrase (which requires entering the old passphrase that contained unicode characters). This did seem to work ok: it let me re-enter the old passphrase (which included unicode characters) to create a new passphrase. However, since this is an empty wallet (and since bitcoin-qt would ask for the passphrase only when attempting to actually spend from an encrypted wallet), I did not see a way to fully test whether the passphrase actually worked to decrypt a unicode-passphrase-encrypted wallet for the purpose of spending from it. (I'm still downloading the rest of the blockchain and it's going to take at least another week on my slow connection, so don't see how I could send a small amount to the new wallet to test it either. My existing wallet.dat file was originally created on an internet-connected machine a long time ago, but it's been offline ever since, so in some sense it's kinda-sorta been in somewhat "cold" storage all this time, and I would prefer to avoid putting it online on a "hot" internet-connected machine until absolutely necessary.) (b) Long-term, I am actually also in the process of setting up a proper cold storage system based on Armory, which I have installed on 2 Ubuntu machines (one offline and one online). But I have a slow internet connection, and the backups of this old wallet.dat file have been sitting around unencrypted for ages (I've been relying simply on then being physically inaccessible). Now some "things" are coming up over the next few days where I some better security right away, and it's probably going to take over a week for Armory/bitcoind to update my local copy of the blockchain. So in the meantime, I also need some basic additional security right now - so encrypting the existing bitcoin-qt wallet.dat file using a strong passphrase (and making some new backups) seems like it could be a reasonable initial approach. Thanks for any help!
[uncensored-r/Bitcoin] [Question] Opening a backup 'wallet.dat' to check it's balance
The following post by HawkEy3 is being replicated because the post has been silently removed. The original post can be found(in censored form) at this link: np.reddit.com/ Bitcoin/comments/7a0f9p The original post's content was as follows:
Hello, I think I'm doing this right but I'd like to be 100% sure. I have the up-to-date bitcoin core v.0.15.0.1 running windows7 and almost synced. The software shows the balance of whichever 'wallet.dat' is in it's directory, right? There are no hidden stumbling block like having to run the bitcoin-qt.exe with -rescan or -updatewallet (for an old wallet file) commands? Or a mandatory import wallet process? And if so, how to do that correctly? -Thanks
PSA: Added Step May Be Needed When Restoring a Backup Encrypted wallet.dat to Bitcoin Core
TL;DR: To successfully restore an encrypted wallet.dat file, the instance of Bitcoin Core getting restored to needs to first have Encryption turned on and possibly the same Passphrase set as the wallet.dat file you are restoring. It seems this must be done before you restore your encrypted wallet.dat from backup, or Bitcoin Core will just show a zero balance. For the record, the set-up for this situation was as follows: Bitcoin Core (formerly Bitcoin-Qt) 0.9.2.1, Windows x86 version, on Windows XP Pro patched for 2019 PoS updates. Recently, my Bitcoin Core hot wallet had been acting up and crashing after about 6 to 12 hours of uptime. I thought that there was possibly some corruption in Core's database files, so I backed up my wallet.dat and started deleting block chain data/index files to see if a rescan or reindex would correct the problem. I tried to save time by not deleting everything, only certain file types. I managed to somehow screw up and got the dreaded "wallet.dat corrupt, salvage failed" message. Since I had a backup, I didn't bother trying the "-salvagewallet" command-line option (which might have actually corrected my problem.) Instead, I went straight for a restore from backup. Some time ago, and on a much older version of Bitcoin-Qt I had familiarized myself with the wallet.dat backup and restore process. I never had a problem with it. But thinking back, I may have done all of my testing with unencrypted wallet.dat files. In this case, I uninstalled Core, deleted everything in the Bitcoin data directory, reinstalled Core, used bootstrap.dat to catch up as much of the block chain as possible, and let the new install finish syncing from the Internet. Once Core was up-to-date, I closed it and restored my encrypted wallet.dat from backup. In my previous experience, I'd be done at this point. The next time I started the wallet, it would have automatically rescanned, and I'd be back in business. This time, when the wallet finally started up again, it showed no errors, the block chain was still fully synced up, but the wallet showed a zero balance. Not a good feeling. I thought maybe I'd need to manually start Core using the "-rescan" command-line option. I tried this, but got the same result. After mulling things over, I finally guessed that the problem might have something to do with Core's wallet.dat encryption. I again deleted the wallet.dat file from the Bitcoin data directory and restarted Core. Once it finished generating a new wallet.dat file, I enabled Encryption and set the same Passphrase as the wallet.dat file I was trying to restore. Core shut itself down to complete encrypting the new wallet.dat file. Next, I started Core once again to make sure all was OK with new encrypted but empty wallet.dat. I then closed Core and replaced the zero-balance wallet.dat file with my recent backup. That finally did the trick. On the next start, Core automatically did a rescan and my balance reappeared. I don't know for sure if this behavior is the same across all the different flavors of Bitcoin Core 0.9.2.1 (x64, OSX, Linux), but I suspect it might be. Also, it might work just to enable Encryption, but it might not be necessary to have the same Passphrase. I can only confirm that it worked in my case with the same Passphrase. This little adventure was unnerving, particularly since Core issues no errors and just insists there's a zero balance. I thought I should relate what I learned in case someone else encounters the same situation. Cheers, and to the moon! EDIT: At least a couple posts so far report not seeing the same behavior I did. I'm glad if it's a non-issue, and I can't explain why it happened to me. I can just suggest if you have similar issues, it might be worth it to give this method a try.
Das Backup Ihrer Brieftasche kann Sie vor Computerfehlern und vielen menschlichen Fehlern schützen. Nachdem Ihr Handy oder Computer gestohlen wurde, können Sie auch Ihr Bitcoin-Wallet wiederherstellen, wenn Ihre Brieftasche verschlüsselt bleibt. Ihre Bitcoin-Dateien (inklusive der Wallet-Datei "wallet.dat") werden irgendwo auf der Festplatte Ihres Computers gespeichert, was Sie kaum wahrnehmen können. Wenn Sie das Datenverzeichnis oder den Speicherort der Bitcoin-Dateien kennen, können Sie das Bitcoin Wallet wiederherstellen oder reparieren, nachdem sie verloren gegangen sind, gelöscht oder beschädigt werden. If you're the owner of some, or a lot, of bitcoin, you may want to know how to backup bitcoin. After all, there is very little tying you to your cryptocurrency of choice, so one tiny mishap could ... locate wallet.dat. Die handlichste Backup-Methode unter Linux ist vermutlich, die wallet.dat auf eine bzw. mehrere dafür verwendete USB-Sticks bzw. Speicherkarten zu kopieren, die an einem sicheren Ort (feuersicherer Tresor, Banksafe, Aquarium mit Piranhas, etc) aufbewahrt werden. Individuelle Verschlüsselung der wallet.dat Shut down the Bitcoin program. Copy your backed-up wallet.dat into your bitcoin data directory. If you are copying in a backed-up wallet.dat that was last used on a Bitcoin version prior to 0.3.21 into an existing profile, delete files blk*.dat to make the client re-download the block chain. You may also need to do this if your transactions don ...
Make some extra $$ lending: Signup for DavorCoin: https://goo.gl/ppsrur OR Signup for Bitconnect: https://goo.gl/xvvhGk This is a short video on setting up, ... Wallets Part 3: Private Key Vs. Wallet.Dat and How To View Navcoin Private Key - Duration: ... Install, Backup And Restore A Bitcoin Wallet. Or, Almost Any CryptoCoin Wallet (Windows) - Duration ... paste wallet.dat file back into grey cwallet Bitcoin Wallet.dat with Password. Here , We have a Bitcoin "wallet.dat" file with Passphrase key and 8.50011 BTC Balance. Private Key and Passphrase Key Is Available. Made by request, this video is just a quick tutorial that walks through how to replace the cryptocurrency Rupee wallet wallet.dat file with a backup you had previously made. This tutorial includes ...