Bitcoin Forum

Where do you store your wallet.dat backup and why? Second disk, usb flash drive, cloud (dropbox, skydrive etc.)? Or maybe you base64encode and print it :P?

Second disk, once a week with my auto backup.

Why? I'm just to lazy to do more and it seems save enough.

On a truecrypt drive. And I backup the truecrypt container frequently, on multiple online locations (dropbox, an FTP server, several webmail addresses, etc).

GPG encrypted (TrueCrypt isn't really meant for single files), on an external hard drive, several flash drives, my camera, my dumbphone, my email account, and a good old-fashioned 3.5" DS/HD floppy disk. These devices are all stored in various physical locations. I'm not taking any chances.

Second hard drive, couple different flash drives, and a netbook that I keep at my friend's house just in case mine burns down :'(. Flash drives and netbook are stored as Truecrypt volumes. Don't keep your wallets hosted at a cloud/dropbox unless it's encrypted/hidden or some shady admin will just take it.

I store mine on a USB drive...I haven't accumulated that many bitcoins yet though so I'm not super protective of it...more worried about my Windows install getting messed up so that's why I back it up to a thumb drive.

On flash chip, which has copies of my 'can't lose' documents and media on it.

Also a paper copy in the safe.

Bank vault

Daily encrypted backup to USB, Dropbox and S3.

Encrypted copies in two different continents. Thrusted third-person timelock strategy in case of amnesia, abduction or death. No safe boxes or vaults.

Thinking in a secure way of applying SSSS for a brainwallet seed.

Be careful though. Suppose someone would manage to copy it, they got your private keys (even for future addresses, if you use the default Bitcoin-Qt client).
So even if there's not much money on there yet, they just may be waiting patiently. Once you have accumulated a truckload of coins, they may decide it's time to cash out, aaaaand -poof- it's gone :)

How did you set this up?

What's that ??? (I mean the SSSS thing)

Rudimentary, but it works:
https://bitcointalk.org/index.php?topic=46489.msg553632#msg553632


Shamir's Secret Sharing Scheme
http://point-at-infinity.org/ssss/
http://point-at-infinity.org/ssss/demo.html

Thanks for the advice  :) You're right, I'll have to figure out a better way to secure it so I've been reading some of the helpful guides here. On a side note, someone would be waiting forever to swoop in and take them at the rate I'm mining  ;D

Inside a faraday cage in-case an EMP fucks the US.

Also on MicroSD, CD, Floppy, other HDD, and a few other places.

Excellent advice about using a faraday cage, the first time anyone has mentioned this in all the security threads I've seen.

Paper wallets would also be good protection against this.

First I have created a number of keys in my wallet, as place holder for later use.

Second I encrypted my wallet with a strong password. It's against theft.

Then I saved the wallet file on at least 3 USB sticks, and distributed them over different locations. It's against damage or destruction.

If I wished to use clouds, I would use truecrypt also.

My problem at this time is: How can I transfer the wallet password (with description) to my relatives in case of death of me and my girlfriend (through accident, for example).

Got my wallet on different hdd`s - no flash drives (had a flashdrive with important data which wasnt accessable after 1 year, so hdd`s only for backup)

Most recently /dev/null - gladly it was just 0.001 BTC, but need to be more careful from now on :)

Just a quick note, but sort of on topic. You can use your microwave as a sort of quick faraday cage. They're built to keep microwaves inside, but also work at keeping a wide range of other frequencies out. So if you need quick protection, you can throw some electronics in it, and it might work depending on your situation.

Mine too, and I've been thinking about a scheme (see post above) that reveal the private keys only after the fact, not before.

But I don't have enough knowledge about nLocktime to do this slickly.