public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "U.Mutlu" <for-gmane@mutluit.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Securing wallet on paper
Date: Thu, 22 Jan 2015 10:36:23 +0100	[thread overview]
Message-ID: <m9qgan$bk1$1@ger.gmane.org> (raw)

I don't know yet the details of how a wallet looks like internally,
but I think it should be possible to print the wallet incl. acct nbr
out on classical paper (as base16 or base64 etc.) for filing it
in a physical home or bank safe.

Later, typing it from paper to a small converter program that recreates the 
wallet file.

IMO this is a good security against possible computer hardware disasters.

Of course one has to secure this further with encryption against bank 
fraud/theft etc.
Ie. the output on paper should be encrypted, and the owner
should place the key somewhere else.

I would suggest the developers make such functionality available for the user.

cu
Uenal




             reply	other threads:[~2015-01-22  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  9:36 U.Mutlu [this message]
2015-01-22  9:46 ` [Bitcoin-development] Securing wallet on paper Pavol Rusnak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='m9qgan$bk1$1@ger.gmane.org' \
    --to=for-gmane@mutluit.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox