Bitcoin Forum
May 27, 2024, 07:03:41 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Using Bitcoin-qt safely offline  (Read 690 times)
Jellybean (OP)
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
February 05, 2013, 06:44:52 PM
Last edit: February 05, 2013, 07:17:04 PM by Jellybean
 #1

Hi everyone,
I posted here couple of days ago, and got advised to use bitaddress.org, however, I'm not 100% confident with it, so I thought about something else for a savings ONLY account. Since Bitcoin-qt created by Satoshi, I believe it should be safer to use it, right?

1. Disconnect internet
2. Run ubuntu from LIVE CD
3. Open bitcoin-qt, close it
4. Open bitcoin-qt, Generate a few addresses, copy them to a txt file,  copy the addresses to 2 USB devices, write them down on paper, etc
5. Export Secret keys from wallet, write them down on a paper
6. Turn OFF PC
7. Check the blockexplorer - each transfer to each address to see if btc received


I  won't encrypt and won't save the .dat to ensure that if there's a keylogger on my pc, it won't get the info.
What's your opinion guys?
Thanks!
DannyHamilton
Legendary
*
Offline Offline

Activity: 3402
Merit: 4656



View Profile
February 05, 2013, 07:04:43 PM
 #2

Hi everyone,
I posted here couple of days ago, and got advised to use bitaddress.org, however, I'm not 100% confident with it, so I thought about something else for a saving ONLY account. Since Bitcoin-qt created by Satoshi, I believe it should be safer to use it, right?

1. Disconnect internet
2. Run ubuntu from LIVE CD
3. Open bitcoin-qt, close it
4. Open bitcoin-qt, Generate a few addresses, copy them to a txt file,  copy the addresses to 2 USB devices, write them down on paper, etc
5. Export Secret keys from wallet, write them down on a paper
6. Turn OFF PC
7. Check the blockchain after each transfer to each address to see if btc received

What's your opinion guys?
Thanks!
Be very careful to make sure that your record the private keys correctly.  If you can't read your writing later, or you accidentally write the private key down wrong, you might not be able to access the bitcoins.  Other than that, it sounds like it will work.
wiggi
Sr. Member
****
Offline Offline

Activity: 403
Merit: 251


View Profile
February 08, 2013, 05:06:57 PM
 #3

Hi everyone,
I posted here couple of days ago, and got advised to use bitaddress.org, however, I'm not 100% confident with it, so I thought about something else for a savings ONLY account. Since Bitcoin-qt created by Satoshi, I believe it should be safer to use it, right?

1. Disconnect internet
2. Run ubuntu from LIVE CD
3. Open bitcoin-qt, close it
4. Open bitcoin-qt, Generate a few addresses, copy them to a txt file,  copy the addresses to 2 USB devices, write them down on paper, etc
5. Export Secret keys from wallet, write them down on a paper
6. Turn OFF PC
7. Check the blockexplorer - each transfer to each address to see if btc received


I  won't encrypt and won't save the .dat to ensure that if there's a keylogger on my pc, it won't get the info.
What's your opinion guys?
Thanks!

LIVE CDs should be guaranteed free of keyloggers, or everything is already lost.
Check the MD5 of the CD.
If it can log your keys (while offline) it can copy unencrypted wallet.dat too.

Secret keys on paper is less safe than wallet file in truecrypt container. Even a
human-memorable password makes it safer, attacker has to hack you *and* need
physical access to your backups.
mjc
Hero Member
*****
Offline Offline

Activity: 588
Merit: 500


Available on Kindle


View Profile WWW
February 08, 2013, 07:31:52 PM
 #4

In addition to what's already been noted, you could place the data which includes the block chain and wallet.dat in a secure drive.  Only mount the drive when you want to sync the interact with the wallet or sync with the blockchain.  You could use the blockchain.info online wallet with Multi Factor Authentication.  I cover both in Bitcoin Step by Step.

Kindle : Bitcoin Step by Step (2nd Ed) : http://www.amazon.com/Bitcoin-Step-by-ebook/dp/B00A1CUQQU
Kindle : Bitcoin Mining Step by Step : http://www.amazon.com/Bitcoin-Step-by-ebook/dp/B00A1CUQQU
Facebook :  https://www.facebook.com/BitcoinStepByStep     Twitter : @BitcoinSbS
blockgenesis
Sr. Member
****
Offline Offline

Activity: 285
Merit: 250

Bitcoin.org maintainer


View Profile
February 09, 2013, 12:36:18 AM
 #5

Secret keys on paper is less safe than wallet file in truecrypt container. Even a
human-memorable password makes it safer, attacker has to hack you *and* need
physical access to your backups.

That being said, encryption is also pretty secure against yourself if you forget your password. Which tends to happen more often with passwords that are not used on a regular base (exactly like this scenario of a offline use).

It might also be a good idea to have a copy in different location, not just at home. One physical location is a single point of failure.

Donation: 18XXXQs1vAQGBAZbXKA322r9Zy1nZac2H4
UnsignedFloat
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 10, 2013, 05:41:53 PM
 #6

Secret keys on paper is less safe than wallet file in truecrypt container. Even a
human-memorable password makes it safer, attacker has to hack you *and* need
physical access to your backups.

That being said, encryption is also pretty secure against yourself if you forget your password. Which tends to happen more often with passwords that are not used on a regular base (exactly like this scenario of a offline use).

It might also be a good idea to have a copy in different location, not just at home. One physical location is a single point of failure.

Just for fun I carved a private key into a bar of gold and put it in the firesafe. Then I've written a small procedure to graph their relative value over time, and I update it every morning.

It will be interesting to see which part is more valuable in the end...
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!