Bitcoin Forum
December 15, 2024, 07:20:31 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: What would happen?  (Read 1330 times)
btc123 (OP)
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
May 19, 2012, 01:17:53 AM
 #1

The balance in my wallet fluctuates up and down quite a bit.  I backup my wallet maybe once every couple of weeks.
What would happen if my computer crashed and I restored a wallet that has more bitcoins in it than the wallet that I lost?

Would the system know which coins I no longer hold or would my transactions fail a lot?
evoorhees
Legendary
*
Offline Offline

Activity: 1008
Merit: 1023


Democracy is the original 51% attack


View Profile
May 19, 2012, 01:27:41 AM
 #2

The wallet backup will still know how many coins you're supposed to have, as long as you haven't created more than 100 btc addresses.   So, if you're only using one address to send/receive, then you can make a backup and come back years later and that backup will show your entire transaction record since then.

This is because your wallet doesn't actually hold "coins" in it, but rather it holds a key to access the coins in the Blockchain. Since the blockchain always knows how much money you have, the wallet backup will discover that information once it's plugged back in.
BadBear
v2.0
Legendary
*
Offline Offline

Activity: 1652
Merit: 1128



View Profile WWW
May 19, 2012, 01:29:13 AM
 #3

What will really happen is you'll restore the wallet file, and the bitcoin client will use the blockchain to verify and update the latest transactions and your current balance. Once a transaction is in the blockchain, it can't be undone.

Think of it as more like a ledger system, your wallet doesn't really contain any bitcoins, just private keys that are verified by the network as possessing those coins.

1Kz25jm6pjNTaz8bFezEYUeBYfEtpjuKRG | PGP: B5797C4F

Tired of annoying signature ads? Ad block for signatures
btc123 (OP)
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
May 19, 2012, 01:32:16 AM
 #4

Good to know, thank you.  Why is there a hard limit at 100 and what happens if I go over 100?
Several forums that I've read recommend that I use a new address for each transaction.  That would add up real quick.
BladeMcCool
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
May 19, 2012, 01:51:35 AM
 #5

the client will create more addresses automatically but those new ones wont be in your old backup so you'll need to make a new backup if you use more. i think it generates them 100 at a time but i could be wrong. this is the default satoshi client i'm talking about anyhow.
Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
May 19, 2012, 02:26:45 AM
 #6

Good to know, thank you.  Why is there a hard limit at 100 and what happens if I go over 100?
Several forums that I've read recommend that I use a new address for each transaction.  That would add up real quick.

The client tries to keep 100 unused private keys available in a "key pool".  So the first time an address from your wallet receives a payment the client then marks that address as being used which brings the number of addesses in the key pool below 100.  The client then adds a new one automatically.

You can specify on startup a size of the keypool so that the client will keep a greater number or fewer number of unused keys.
 - http://en.bitcoin.it/wiki/Key_pool

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


beckspace
Hero Member
*****
Offline Offline

Activity: 931
Merit: 500


View Profile
May 19, 2012, 04:49:56 AM
 #7


The client tries to keep 100 unused private keys available in a "key pool".  So the first time an address from your wallet receives a payment the client then marks that address as being used which brings the number of addesses in the key pool below 100.  The client then adds a new one automatically.


Is this true?

I always thought that if I had a backup that was in address 98 (for example), and used the client until address 110 and lose the wallet.dat at that point I'd be screwed.

I thought that the client generated another 100 addresses at once just when the number 100 was reached, good to know it's not that way.
notme
Legendary
*
Offline Offline

Activity: 1904
Merit: 1002


View Profile
May 19, 2012, 04:51:57 AM
 #8


The client tries to keep 100 unused private keys available in a "key pool".  So the first time an address from your wallet receives a payment the client then marks that address as being used which brings the number of addesses in the key pool below 100.  The client then adds a new one automatically.


Is this true?

I always thought that if I had a backup that was in address 98 (for example), and used the client until address 110 and lose the wallet.dat at that point I'd be screwed.

I thought that the client generated another 100 addresses at once just when the number 100 was reached, good to know it's not that way.

Yes... the idea of a key pool is is to keep the pool full.  Swimming on concrete is no fun.

https://www.bitcoin.org/bitcoin.pdf
While no idea is perfect, some ideas are useful.
beckspace
Hero Member
*****
Offline Offline

Activity: 931
Merit: 500


View Profile
May 19, 2012, 05:31:37 AM
 #9

The balance in my wallet fluctuates up and down quite a bit.  I backup my wallet maybe once every couple of weeks.
What would happen if my computer crashed and I restored a wallet that has more bitcoins in it than the wallet that I lost?

Would the system know which coins I no longer hold or would my transactions fail a lot?


It's a prudent practice always use new addresses and backup your wallet not every couple of weeks, but every 50 transactions or so (Keep your fuel tank at least half full).

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!