Topic: Backup of encrypted wallets: are they encrypted, too? (Read 1541 times)
Good to know
Thank you for the clarification turvarya. Normally i would have thought that the standard client will create the same addresses again. So when 100 are not enough and he creates more 100 then it would not be a problem when there is only a backup for the first 100. The second 100 could be created from seed.
I wonder why that doesn't happen.
As far as I know, there just wasn't something like this seed passed generation of private keys, as e.g. Mycelium uses, when Bitcoin QT was created.I wonder why that doesn't happen.
Bitcoin Core just randomly generated addresses without any connection to each other.
That's good to know but sounds like the official client is inferiour to alternative clients. Or did the official client update it's technique so that is using seeds too now?
If you use bitcoin core and expect to create lots of addresses, you could use -keypool=
FYR: https://en.bitcoin.it/wiki/Running_Bitcoin
Nope bitcoin core doesn't use a seed and is not deterministic.
Thank you for the clarification turvarya. Normally i would have thought that the standard client will create the same addresses again. So when 100 are not enough and he creates more 100 then it would not be a problem when there is only a backup for the first 100. The second 100 could be created from seed.
I wonder why that doesn't happen.
As far as I know, there just wasn't something like this seed passed generation of private keys, as e.g. Mycelium uses, when Bitcoin QT was created.I wonder why that doesn't happen.
Bitcoin Core just randomly generated addresses without any connection to each other.
That's good to know but sounds like the official client is inferiour to alternative clients. Or did the official client update it's technique so that is using seeds too now?
When you add a passphrase to Bitcoin Core, it throws out all unused addresses in the pool, so any previous backups are no longer valid because they have the wrong keys. You must back up the wallet after adding a passphrase, just like the instructions say.
So, adding a passphrase creates new address and send all funds from previously created addresses to the new addresses?So, I used address 1-10 and than made a backup. The backup contains all 100 addresses. Then I used address 11-20 and came to mind, that I should encrypt the whole thing. According to you, it deleted address 21-100 and creates new addresses. It still has address 1-20 which could contain money and which are in the backup. I could even have given out one of these addresses for let's say weekly payments of a sig campaign here on the forum and would get Bitcoin in the future.
Only money that is send to new addresses is save.
So, I am still right about, deleting your old backups after encrypting your wallet.
it should only delete those addresses that are not between those 100 in the pool if i'm not mistaken if they are between the 100 addresses they are safe no need to do a back up again
Bitcoin Core generates 100 addresses in advance. So, if you back it up, just this addresses get backed up. If you used all 100 addresses, it generates 100 new ones. If you back up now, all 200 are saved.
The problem is(afaik, maybe it changed), that it doesn't tell you, that it generated new addresses und your backup is outdated.
The problem is(afaik, maybe it changed), that it doesn't tell you, that it generated new addresses und your backup is outdated.
it does not make sense to back up the unused address if you used all 100 first one sot he next 100 ar enot back in the back up or maybe i'm missing something
Thank you for the clarification turvarya. Normally i would have thought that the standard client will create the same addresses again. So when 100 are not enough and he creates more 100 then it would not be a problem when there is only a backup for the first 100. The second 100 could be created from seed.
I wonder why that doesn't happen.
As far as I know, there just wasn't something like this seed passed generation of private keys, as e.g. Mycelium uses, when Bitcoin QT was created.I wonder why that doesn't happen.
Bitcoin Core just randomly generated addresses without any connection to each other.
Thank you for the clarification turvarya. Normally i would have thought that the standard client will create the same addresses again. So when 100 are not enough and he creates more 100 then it would not be a problem when there is only a backup for the first 100. The second 100 could be created from seed.
I wonder why that doesn't happen.
I wonder why that doesn't happen.
backupwallet is the same as copying wallet.dat
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
Wasn't there a bug in a previous version of bitcoin-qt where the backup did only back up the first hundred bitcoin addresses so that the ones coming after that were not backed up. Then does this mean the backing up procedure of the wallet.dat did change?
It is not a bug and it is same for latest versions AFAIK.
The problem is(afaik, maybe it changed), that it doesn't tell you, that it generated new addresses und your backup is outdated.
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
backupwallet is the same as copying wallet.dat
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
Wasn't there a bug in a previous version of bitcoin-qt where the backup did only back up the first hundred bitcoin addresses so that the ones coming after that were not backed up. Then does this mean the backing up procedure of the wallet.dat did change?
It is not a bug and it is same for latest versions AFAIK.
backupwallet is the same as copying wallet.dat
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
Wasn't there a bug in a previous version of bitcoin-qt where the backup did only back up the first hundred bitcoin addresses so that the ones coming after that were not backed up. Then does this mean the backing up procedure of the wallet.dat did change?
When you add a passphrase to Bitcoin Core, it throws out all unused addresses in the pool, so any previous backups are no longer valid because they have the wrong keys. You must back up the wallet after adding a passphrase, just like the instructions say.
So, adding a passphrase creates new address and send all funds from previously created addresses to the new addresses?So, I used address 1-10 and than made a backup. The backup contains all 100 addresses. Then I used address 11-20 and came to mind, that I should encrypt the whole thing. According to you, it deleted address 21-100 and creates new addresses. It still has address 1-20 which could contain money and which are in the backup. I could even have given out one of these addresses for let's say weekly payments of a sig campaign here on the forum and would get Bitcoin in the future.
Only money that is send to new addresses is save.
So, I am still right about, deleting your old backups after encrypting your wallet.
When you add a passphrase to Bitcoin Core, it throws out all unused addresses in the pool, so any previous backups are no longer valid because they have the wrong keys. You must back up the wallet after adding a passphrase, just like the instructions say.
So, adding a passphrase creates new address and send all funds from previously created addresses to the new addresses?
never bothered with encripting it, i know it is useful in the case you wallet is stolen, but i prefer to have access to my fund in the fastes way posssible, i want to cover more the security of my machine and no the wallet itself
having a machine that is not infected in the first place(one can argue that you never know if it infected, well he is wrong, you can.. with a simple "trap wallet" and with the fact that i don't DL anything without a sign) is the most important thing for me
having a machine that is not infected in the first place(one can argue that you never know if it infected, well he is wrong, you can.. with a simple "trap wallet" and with the fact that i don't DL anything without a sign) is the most important thing for me
Shit, I knew I was right the first time before I said I was wrong
backupwallet is the same as copying wallet.dat
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
Wrong.encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
The wallet.dat is designed to fit in every installation of Bitcoin Core.
Your scenario just means, you made an unencrypted backup, before encrypting it, so your encryption was pointless if somebody finds the backup.
If you encrypt your wallet, you should delete all unencrypted backups(so all backups, that were made before the encryption)
Wrong.
When you add a passphrase to Bitcoin Core, it throws out all unused addresses in the pool, so any previous backups are no longer valid because they have the wrong keys. You must back up the wallet after adding a passphrase, just like the instructions say.
backupwallet is the same as copying wallet.dat
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
Wrong.encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
The wallet.dat is designed to fit in every installation of Bitcoin Core.
Your scenario just means, you made an unencrypted backup, before encrypting it, so your encryption was pointless if somebody finds the backup.
If you encrypt your wallet, you should delete all unencrypted backups(so all backups, that were made before the encryption)
Wrong.
When you add a passphrase to Bitcoin Core, it throws out all unused addresses in the pool, so any previous backups are no longer valid because they have the wrong keys. You must back up the wallet after adding a passphrase, just like the instructions say.
correct me if iam wrong but when you use a passphrase your wallet is safe because an attacker has to know that passphrase. only the wallet.dat is useless.
to be even more safe: you can encrypt that wallet.dat too with software tools.
(i know there should not be any keyloggers on your pc)
to be even more safe: you can encrypt that wallet.dat too with software tools.
(i know there should not be any keyloggers on your pc)
That's correct, so before you backup your wallet enter a very strong passphrase and encrypt it! Then you can encrypt with a third party encryption tool (I won't name any!)
correct me if iam wrong but when you use a passphrase your wallet should be safe because an attacker has to know that passphrase. only the wallet.dat is useless.
to be even more safe: you can encrypt that wallet.dat too with software tools.
(i know there should not be any keyloggers on your pc)
to be even more safe: you can encrypt that wallet.dat too with software tools.
(i know there should not be any keyloggers on your pc)
That makes more sense. I knew there was something wrong with the way I said it.
backupwallet is the same as copying wallet.dat
encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
Wrong.encrypting the wallet means encrypting the private keys.
If you have made a backup, and then you encrypt your wallet, you need to make a new backup because the old one will not work anymore.
Anyway that's my understanding, someone please correct me if I'm wrong. And I'm sure I've missed some important points.
The wallet.dat is designed to fit in every installation of Bitcoin Core.
Your scenario just means, you made an unencrypted backup, before encrypting it, so your encryption was pointless if somebody finds the backup.
If you encrypt your wallet, you should delete all unencrypted backups(so all backups, that were made before the encryption)
I don't believe the file is encrypted as well just protected by the passphrase you protected with (If you added one)
The Backup Wallet feature is just a much less technical way for a user to backup their wallets without having to navigate through user folders and temp folders etc.
I do believe a routine 'Please Backup Your Walket' message should appear in the Bitcoin client or something similar in design.
The Backup Wallet feature is just a much less technical way for a user to backup their wallets without having to navigate through user folders and temp folders etc.
I do believe a routine 'Please Backup Your Walket' message should appear in the Bitcoin client or something similar in design.
Jump to: