Cool, thanks! I'll keep a very safe backup(s) of my wallet from day one then, and from then on not worry about the wallet.dat file bitcoin uses, as if I somehow lose it, I will always be able to use the day 1 backup.

Thanks a lot deepceleron! Funnily enough, throughout all my research googling and learning about bitcoins, your name has popped up in many of the threads matching my search terms dating long back - you have indirectly helped me more than you think ^^

Anyway, I have a new idea for my setup, does this sound ok?

- I create 2 wallets, and back them up to my encrypted container stored on dropbox.
- I create a second encrypted container to store my datadir.
- When I want to swap between the two wallets, I ensure bitcoin.exe is completely shut down, I then proceed to delete all files in the datadir except: wallet.dat, blk0001.dat, blkindex.dat andbitcoin.conf.
- I then replace wallet.dat with the other wallet, and rerun bitcoin.exe (always with -rescan) on a new Tor identity.

I really want to avoid having a second computer or second database

Also, a hypothetical question as there is something I am unsure about in regards to the wallet.dat file: If I create an offline backup of my wallet.dat on day 1, can I restore that day1 wallet.dat 500 days later after plenty of usage of my wallet, and still be fully functional with all my bitcoins? Or do I always have to have an "up-to-date" backup of my wallet.dat?

One final question actually, is it still safe enough to symbolic link the blockchain outside of my encrypted container?

It is so HUGE and I want to be able to store my encrypted container inside dropbox. Moving the database folder outside would solve that...

But does the %bitcoinuserdir%\database folder contain any sensitive info?

If someone were to examine the database folder I redirect to my regular harddrive, would they be able to attain any info about my wallets or transactions?

I guess I could create a second container solely for the purpose of storing the blockchain, but I would preferably like to avoid this if there is no sensitive information in that folder anyway ....

Wow, I hate when the simple solution is right in front of me yet I go on thinking way too complicated for no reason -.-

But this is great... I use one client... 2 seperate wallets... Open client with wallet 1, finish business, close program, get new tor identity, replace wallet with 2nd one, open client, finish business, and I'm good!

Thanks a lot hehe

What oO, you didn't read my post did you

Hello.

I am aware that bitcoin is pseudonymous and transactions can be backtraced to ones IP address. I am therefore putting in some effort to deny this possibility to become as anonymous as possible.

With that said - my strategy is to use 2 separate wallets, which will run through tor on separate identities. I will receive money on one wallet, tumble it to my second, and on a new tor identity, login to the second wallet where I will transfer to the final destination wherever that may be.

There is one issue I am experiencing though - downloading the blockchain through Tor takes FOREVER! (and is not so nice either to the other people using Tor)

I finished doing it once for my first wallet, and I am now wondering whether or not I can create a symbolic link to a central "database" folder.

From the technical aspect, I imagine something like this: I have my bitcoindatawallet1 folder & bitcoindatawallet2 folder. Inside both of these folders are a symbolic link called "database" pointing towards a central blockchain.

Considering I will -never- have both clients running at the same time (which obviously then could cause corruptions or something else weird), can this idea of mine pose any implications or security risks? Will it even work?

Another big bonus is that I would then be able to store the blockchain outside of my encrypted container, so it isn't as huge as it is now (I could then store the container on dropbox).

Thanks