Bitcoin Forum
May 04, 2024, 08:22:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Backing up in bitcoin-qt and litecoin-qt  (Read 2422 times)
btcxyzzz (OP)
Legendary
*
Offline Offline

Activity: 888
Merit: 1000

Monero - secure, private and untraceable currency.


View Profile WWW
April 02, 2013, 01:07:44 PM
 #1

If I backup my wallet and then change is made, and then I loose the wallet with that recent change, if I restore wallet, will I have the funds that I had before change? In other words: I'm bored to backup after just a small positive changes like profit from mining, if I'm able to restore majority of my coins, I wouldn't do backup after every change...

Hope someone understands my question... :)

Token Bubbles – Transforming the ICO Rating and Analysis Space.
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714854142
Hero Member
*
Offline Offline

Posts: 1714854142

View Profile Personal Message (Offline)

Ignore
1714854142
Reply with quote  #2

1714854142
Report to moderator
wumpus
Hero Member
*****
Offline Offline

Activity: 812
Merit: 1022

No Maps for These Territories


View Profile
April 02, 2013, 02:48:36 PM
 #2

You don't need to backup after every change; the wallet has 100 (=keypoolsize) spare keys. Every time you send coins or create a receiving address you will use one of those, so it depends on how actively you use the wallet how often you need to backup.

Bitcoin Core developer [PGP] Warning: For most, coin loss is a larger risk than coin theft. A disk can die any time. Regularly back up your wallet through FileBackup Wallet to an external storage or the (encrypted!) cloud. Use a separate offline wallet for storing larger amounts.
DannyHamilton
Legendary
*
Offline Offline

Activity: 3388
Merit: 4616



View Profile
April 02, 2013, 03:01:23 PM
 #3

You don't need to backup after every change; the wallet has 100 (=keypoolsize) spare keys. Every time you send coins or create a receiving address you will use one of those, so it depends on how actively you use the wallet how often you need to backup.

One exception to this rule is regarding encryption.  When you encrypt your wallet (or change your password), Bitcoin-Qt discards all addresses in the keypool and generates 100 new addresses.  So, if you encrypt or change your password, you should immediately create a new backup.
wumpus
Hero Member
*****
Offline Offline

Activity: 812
Merit: 1022

No Maps for These Territories


View Profile
April 02, 2013, 03:04:30 PM
 #4

You don't need to backup after every change; the wallet has 100 (=keypoolsize) spare keys. Every time you send coins or create a receiving address you will use one of those, so it depends on how actively you use the wallet how often you need to backup.

One exception to this rule is regarding encryption.  When you encrypt your wallet (or change your password), Bitcoin-Qt discards all addresses in the keypool and generates 100 new addresses.  So, if you encrypt or change your password, you should immediately create a new backup.
Good point indeed.

Bitcoin Core developer [PGP] Warning: For most, coin loss is a larger risk than coin theft. A disk can die any time. Regularly back up your wallet through FileBackup Wallet to an external storage or the (encrypted!) cloud. Use a separate offline wallet for storing larger amounts.
btcxyzzz (OP)
Legendary
*
Offline Offline

Activity: 888
Merit: 1000

Monero - secure, private and untraceable currency.


View Profile WWW
April 03, 2013, 03:01:46 PM
 #5

Thanks, if only anyone could explain "the wallet has 100 (=keypoolsize) spare keys", that would be nice...

Token Bubbles – Transforming the ICO Rating and Analysis Space.
DannyHamilton
Legendary
*
Offline Offline

Activity: 3388
Merit: 4616



View Profile
April 03, 2013, 03:31:38 PM
 #6

Thanks, if only anyone could explain "the wallet has 100 (=keypoolsize) spare keys", that would be nice...

Does this explain it any better?

Ok, so I backup my wallet and store it somewhere.

Then in my client, I create a new address to receive coins and have some money sent my way.

Do I need to backup my wallet again because I have created a new address?

That depends on which wallet program you are using, but in most cases the answer is no.

If you are using Bitcoin-Qt with the default configuration, it pre-generates the next 100 addresses that it will use and stores them in the wallet.dat file.  This means that new address that you "created" was already in the wallet.dat when you backed it up (as will be the next 99 addresses "created" after that).  Each time Bitcoin-Qt pulls an address from the pool of pre-generated addresses, it pre-generates another address and adds it to the pool so that there are always 100 "future" addresses in any new backup.

There are 2 things to be aware of if you are going to rely on this pre-generation of addresses.

First, when you add (or change) a password to the wallet it tosses out all 100 of the pre-generated addresses and generates 100 new ones.  This means that if you back-up the wallet, then add a password, and then "create" a new address to receive coins, the backup will not have the address and will be unable to access those coins.

Second, Bitcoin-Qt uses one of those pre-generated addresses without telling you about it every time you create a transaction to send bitcoins.  This address is kept hidden from you, and is used to store the "change" from the transaction.  Bitcoin-Qt will generally try to choose to use more bitcoins from your wallet than are needed for the transaction you are creating, then it will send the excess back to your wallet using this "change" address.  This means you can't just count up the addresses in the "receive coins" tab of the wallet, since additional addresses were used up each time you sent a transaction as well.
Pages: [1]
  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!