Topic: What kind of cold storage do you use? - page 2. (Read 2962 times)
Paper wallets are the only way to go.
Doesn't saving a paper wallet in a computer defeat its purpose, though?
definitely paper wallets
I like to keep mine backed up to a few USBs. I dont really trust paper wallets.
Why? A USB drive will break down far faster than a piece of paper.
EDIT: If you have backups, then don't mind this
I like to keep mine backed up to a few USBs. I dont really trust paper wallets.
i gave mine to satoshi, if he cant be trusted, who can?
I can be trusted.
Or maybe pirate
i gave mine to satoshi, if he cant be trusted, who can?
The problem with a dice-generated hex private key is that you need to convert it to WIF format to be imported into wallet, and that involves some kind of calculation which is not straightforward and can not be done by a simple bash script without calling other external functions like SHA256.
So you call an external function. Why is that a problem?
An external function might be planted with some back door, so that the WIF format key generated only have limited numbers, like millions of keys maximum, so even if you don't generate the same key twice, the hacker can easily scan those millions of keys and see if someone has put bitcoins in them
It's not that easy to hide a backdoor in something as a simple as a cryptographic hash function script. There are already public implementations of this and should be peer reviewed. But more importantly, you can easily verify it using a few random inputs and compare against a separate implementation! If the code looks normal and verifies successfully the hash outputs against other SHA-256 implementations, then it would be extremely unlikely a backdoor would be possible.
If you are familiar with the avalanche effect where changing one character in the input changes the entire output completely, the same thing would happen if you tried to manipulate the output so your verification tests would fail. That's the beauty of the hash function.
Thanks, that is a very good point! If I can verify it gives a correct output for a defined input like other conversion tools, I can even rely on an offline webpage to do the conversion
Adding this verification step will complete the whole process: Dice generate the key and script convert to WIF format, then import into any wallet to get address to send coin to
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
The problem with a dice-generated hex private key is that you need to convert it to WIF format to be imported into wallet, and that involves some kind of calculation which is not straightforward and can not be done by a simple bash script without calling other external functions like SHA256.
So you call an external function. Why is that a problem?
An external function might be planted with some back door, so that the WIF format key generated only have limited numbers, like millions of keys maximum, so even if you don't generate the same key twice, the hacker can easily scan those millions of keys and see if someone has put bitcoins in them
It's not that easy to hide a backdoor in something as a simple as a cryptographic hash function script. There are already public implementations of this and should be peer reviewed. But more importantly, you can easily verify it using a few random inputs and compare against a separate implementation! If the code looks normal and verifies successfully the hash outputs against other SHA-256 implementations, then it would be extremely unlikely a backdoor would be possible.
If you are familiar with the avalanche effect where changing one character in the input changes the entire output completely, the same thing would happen if you tried to manipulate the output so your verification tests would fail. That's the beauty of the hash function.
You told me you didn't have any bitcoins.
Lol.. that is the best thing to do here. Once I posted here that I was having some 4-5 coins with me. My inbox was flooded with emails from beggers very soon. So better keep silent about your stash.
I use a USB key with a fresh Linux install + electrum, used online only to setup.
The problem with a dice-generated hex private key is that you need to convert it to WIF format to be imported into wallet, and that involves some kind of calculation which is not straightforward and can not be done by a simple bash script without calling other external functions like SHA256.
So you call an external function. Why is that a problem?
An external function might be planted with some back door, so that the WIF format key generated only have limited numbers, like millions of keys maximum, so even if you don't generate the same key twice, the hacker can easily scan those millions of keys and see if someone has put bitcoins in them
I do not need a cold storage address yet. I do not own enough to worry about that. If I do, I think I will use electrum. I like the predetermined addresses and the ease of recovery.
http://i.imgur.com/enP4jbnl.jpghttp://i.imgur.com/MP15o2Al.jpg
Fire-proof, Flood-proof, Scratch-proof, BIP0038 protected stainless steel cold storage wallets from CryoBit. Generate new on our site (through bitaddress.org) or supply your own encrypted key/public address pair.
https://bitcointalksearch.org/topic/the-ultimate-cold-storage-solution-cryobits-cryo-card-610540
https://www.cryobit.co
Fire-proof, Flood-proof, Scratch-proof, BIP0038 protected stainless steel cold storage wallets from CryoBit. Generate new on our site (through bitaddress.org) or supply your own encrypted key/public address pair.
https://bitcointalksearch.org/topic/the-ultimate-cold-storage-solution-cryobits-cryo-card-610540
https://www.cryobit.co
Blockchain.info and Coinbase.com don't really qualify as cold storage options, no?
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
The problem with a dice-generated hex private key is that you need to convert it to WIF format to be imported into wallet, and that involves some kind of calculation which is not straightforward and can not be done by a simple bash script without calling other external functions like SHA256.
So you call an external function. Why is that a problem?
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
7 paper wallets, encrypted in a 14 Alphanumeric password stored inside a safe at 7 different locations.
You told me you didn't have any bitcoins.
7 paper wallets, encrypted in a 14 Alphanumeric password stored inside a safe at 7 different locations.
I would advise against that unless those paper wallets are BIP38 encrypted that you do not give them to someone else to print out. Unless it's your family/most trusted friend that your willing to trust your money with I would just be content with a USB stored version. If you have a pen and paper you could also just write it down the old fashioned way - sure it doesn't look so fancy but it really comes to the same thing.
Well... thought about it for a bit... and I have decided to hold on to my USB wallets. Everything is fine as of now, and I don't want to change the equilibrium. So, for now, it is going to be 100% USB wallets for me.
Jump to: