From: Casey Rodarmor <casey@rodarmor•com>
To: "Dâniel Fraga" <fragabr@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Suggestion: easy way to restore wallet.dat backup
Date: Tue, 3 Dec 2013 21:16:18 -0800 [thread overview]
Message-ID: <CANLPe+Ox4zsQQ2nYshtzOHj9biK=YK3C+dcGZ3L_+Tj_HAQv3A@mail.gmail.com> (raw)
In-Reply-To: <l7ld63$25l$2@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
On Tue, Dec 3, 2013 at 11:59 AM, Dâniel Fraga <fragabr@gmail•com> wrote:
>
> Today, when a user uses bitcoin-qt client, it can make a backup
> of wallet.dat easily through menu, but when he/she needs to restore
> this backup, he/she must copy the file to the correct folder and
> execute "bitcoin-qt -rescan".
>
I actually think this is part of a larger and somewhat subtle UX problem
with bitcoin-qt – and, to be totally fair, a whole bunch of other wallet
programs.
I think the issue is that bitcoin-qt should have a document-oriented
approach to wallets. It should make you select a location to store your
wallet, just like a word processor, when you create a new wallet. It could
open the most recent wallet when you run the program, or allow you to open
a wallet by double-clicking it directly in the OS.
I think this would solve this particular issue nicely, just double click
the wallet file. Also, the menu item can just be labeled "Open Wallet". It
might also prevent those kind of heartbreaking posts which read something
like, "I just wiped my hard drive and reinstalled bitcoin-qt, where are my
coins?" People don't have the expectation that if they get Word on a new PC
that their documents will somehow magically be available, I think in part
because Word forces you to deal with the documents and the save location
yourself.
I know that this would bring with it a host of other considerations: Can
multiple wallets be open at the same time? What happens if a wallet file is
moved while it's open? What happens when there are two versions of the same
wallet? Will users understand that they need to backup their wallets
periodically?
But, I think it would be a big enough usability win that it should be
considered. Also, if at the same time bitcoin-qt were to adopt BIP 32 style
deterministically derived private keys from a single seed, a bunch of the
issues above would also go away: There are never two versions of the same
wallet, since they're the same seed, and periodic backups are unnecessary.
[-- Attachment #2: Type: text/html, Size: 2578 bytes --]
prev parent reply other threads:[~2013-12-04 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 19:59 Dâniel Fraga
2013-12-04 5:16 ` Casey Rodarmor [this message]
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='CANLPe+Ox4zsQQ2nYshtzOHj9biK=YK3C+dcGZ3L_+Tj_HAQv3A@mail.gmail.com' \
--to=casey@rodarmor$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=fragabr@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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