BiblePay (BBP) is a Charity Christian Cryptocurrency that donates 10% of coins to Charity every month, sponsoring orphans
WELCOME TO THE WORLD OF CRYPTOCURRENCY! Crypto Australia is a subreddit for Australians and New Zealanders to talk about anything related to crypto.
Don't think I have any significant amount of funds in this wallet, but am curious just what kind of a back up I am looking at. Ideas? submitted by
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. submitted by
I dont wanna install Bitcoin-QT again and download the whole blockchain. submitted by
Is there a simpler way where I download Electrum and transfer those BTC from wallet.dat to the electrum wallet?
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
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
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!
Or does deleting the Bitcoin Core cause issues later with importing, specifically if I downloaded it onto another computer? submitted by
Once the wallet file is encrypted you can now backup this file. 1. Open your wallet, go to File >> Save copy. Name your wallet to anything and store it in different location. You can save this file on a USB drive or an external hard disk and keep it offline. 2. The second method is directly copying the wallet file from the Electrum folder. You ... If you misplace your cold wallet or if your hard drive crashes, you can recall the seed phrase and private key to set up your wallet again. Back up the Entire Wallet. You can backup an entire wallet with all the hidden internal private keys. The private keys linked with your Bitcoin address are not enough to recover the whole amount. There are generally 3 ways to backup a Bitcoin wallet. Different software supports different methods. Make sure you're familiar with your wallet before loading it with bitcoins. If you lose the backup and can't access your wallet for some reasons, your bitcoins are permanently gone! Wallet.dat. This method is used by Bitcoin Core (and few others) and comprises of backing up a wallet.dat file ... You can find the Wallet.dat file in Bitcoin’s data directory. Warning: Keep in mind that the file has different locations based on the operating system. To back up, copy the file onto an external media device such as a USB drive. Go under tools and hit “export private keys.” To restore your backup, copy your backed up wallet.dat over an existing one in the bitcoin data section. How to ... The wallet.dat file is cross platform compatible so you can move across different computer or an operating system. Restoring a backup file to new wallet. First of all we are not going to cover importing private keys for which we’ll make a separate guide. Here we’ll show you how to restore wallet.dat backup file to new wallet client. The ...
This is a step by step guide to using the Bitcoin wallet client. How to download it. How to Encrypt is and protect your Bitcoin. How to back up your wallet a... part two of my tutorial on how to decrypt the android bitcoin wallet to find the seed and transfer it to multibitHD so that you can (if you choose to) claim bitcoin cash (assuming you had bitcoin ... 1 month free. Find out why Close. How to backup your Litecoin Wallet Joe Plummer. Loading... Unsubscribe from Joe Plummer? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 2.9K ... The Crypto Dad shows you how to back up the Electrum Bitcoin wallet. I go through making sure your password is stored in a safe place. Then I talk about prin... Worried about losing your Bitcoins? You shouldn't -- Bitsonline's Daniel Rojas explains how to easily backup and restore your mobile BTC wallet.