Bitcoin Forum
December 10, 2016, 01:36:27 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Database Backup and Wallet isolation  (Read 930 times)
netrin
Sr. Member
****
Offline Offline

Activity: 322


FirstBits: 168Bc


View Profile
May 25, 2011, 08:10:35 PM
 #1

I use (or would like to use) multiple wallets. For example, 1. public and 2. secure/backup. However, because internet usage is very expensive and slow, I want to reuse much of the .bitcoin/database. Simply removing the wallet.dat file (bitcoin.conf keypool=1) and restarting will crash the client on close. Having a theory as to why, I removed both the addr.dat and wallet.dat files and relaunched the BitCoin client.

Are only the addr.dat and wallet.dat files associated with a particular set of address/key pairs?

Is everything else generic distributed database stuff?

Or, as I suspect, is there data related to my wallet and thus my identity still scattered among the files, such as log files and blkindex, etc.

It seems to me data related to my wallet and identity should be distinctly isolated from the public distributed database files. My wallet/identifying data should change at a minimum. In my opinion, generating new addresses for change (even when 0 BTC) is an implementation detail that should either be manual or optional. The default 100 address pool has unexpected consequences, giving a false sense of backup security until perhaps loosing all money much later in time when restoring from backup. The binary nature of the wallet keeps people from merging, spliting, and generally understanding and maintaining their own wallet. If I want to 'launder' money and increase anonymity, I should distribute coins multiple times and at random intervals, not as a predictable operation along with every transaction which decreases my ability to restore from failure.

Greenlandic tupilak. Hand carved, traditional cursed bone figures. Sorry, polar bear, walrus and human remains not available for export.
1481333787
Hero Member
*
Offline Offline

Posts: 1481333787

View Profile Personal Message (Offline)

Ignore
1481333787
Reply with quote  #2

1481333787
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481333787
Hero Member
*
Offline Offline

Posts: 1481333787

View Profile Personal Message (Offline)

Ignore
1481333787
Reply with quote  #2

1481333787
Report to moderator
1481333787
Hero Member
*
Offline Offline

Posts: 1481333787

View Profile Personal Message (Offline)

Ignore
1481333787
Reply with quote  #2

1481333787
Report to moderator
bitpop
Legendary
*
Offline Offline

Activity: 1932


https://keybase.io/bitpop


View Profile WWW
May 26, 2011, 08:48:52 AM
 #2

+1

Reputation  |  PGP  |  DigitalOcean  |  OpenVPN 2GB Free  |  TorGuard  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Bitmessage: BM-2cXN9j8NFT2n1FxDVQ6HQq4D4MZuuaBFyb
netrin
Sr. Member
****
Offline Offline

Activity: 322


FirstBits: 168Bc


View Profile
May 26, 2011, 02:01:58 PM
 #3

I've been playing around switching between wallets in my .bitcoin directory. Three files (wallet.dat, addr.dat, and blkindex.dat are tied to single wallet or need to be rescanned/deleted between wallet swaps). The blk0001.dat file expands linearly with every swap with seemingly no shared/resusable data (which is evident by my now 600 MB blk0001.dat file.

I'm going to assume the lack of block data sharing is a bug or an oversight, but as of bitcoin-0.3.21, a "reusable wallet" consists of nearly the entire datadir (.bitcoin).

I would have assumed the old block chain (from genesis to yesterday) would be static.

Ideally there would be a [database] directory containing the 'static' historical block chain, a [limbo] directory for the not-yet confirmed recent block chain, a [wallet] directory with my addresses, keys, and anything identifying/personal, and finally a [log] directory that can be safely deleted.

And the more files are plaintext, the better. The bottleneck is the network graph and connections, not local file handling. Let the miners optimize, the general user needs to understand and the power to modify.

Greenlandic tupilak. Hand carved, traditional cursed bone figures. Sorry, polar bear, walrus and human remains not available for export.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!