Bitcoin Forum
June 16, 2024, 09:41:18 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: Backup of encrypted wallets: are they encrypted, too?  (Read 1488 times)
TinEye
Hero Member
*****
Offline Offline

Activity: 639
Merit: 500



View Profile
July 27, 2015, 02:02:55 PM
 #21

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?
That still doesn't make sense. From the way, I understand Bitcoin Core, it creates 100 addresses at once.
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.

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



                                                                    ▄▄▄▄▄▄▄▄▄
                                                                   ▄█████████                  ██████
                                                                   ███    ███                 ██   ██
         ████████████████████████████████████████████████████████████    ██████████████████████   ████████▀
        ██            ▄█          █▄                 █▄          ███            █▄          █        ▄██▀
       ██            ██           ███                ██   ▄▄▄▄▄  ███            ██   ▄▄▄▄▄  ██   █████▀
       ██   █████    ██   ████   ████   ██     ██    ██   ▀▀▀▀   ██    ██████   ██   ▀▀▀▀   ██   ████▀
      ██    █████   ██    ████   ████   ██     ██   ██          ███   ██████   ██          ██   ████▀
      ██            ██           ███   ███    ███   ██    ▀▀▀▀▀▀███            ██    ▀▀▀▀▀▀██   ▀▀▀████
      ███           ██▄            █   ██     ██    ██▄          █             ▀█▄          ██      ███
       █████████   ████████████████████████████████████████████████████████████████████████████████████
      ██           ██
    ██▀           ███
  ████████████████▀
peligro
Hero Member
*****
Offline Offline

Activity: 593
Merit: 500


1NoBanksLuJPXf8Sc831fPqjrRpkQPKkEA


View Profile
July 31, 2015, 12:43:04 PM
 #22

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.
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?
Shogen
Legendary
*
Offline Offline

Activity: 966
Merit: 1001



View Profile
July 31, 2015, 12:57:45 PM
 #23

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.
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=<n> to change your key pool size.
FYR: https://en.bitcoin.it/wiki/Running_Bitcoin

Nope bitcoin core doesn't use a seed and is not deterministic.



Nasakloto
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
August 01, 2015, 06:37:35 AM
 #24


Good to know
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!