From: Wladimir <laanwj@gmail•com>
To: Jim <jim618@fastmail•co.uk>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fees UI warning
Date: Mon, 16 Dec 2013 12:37:04 +0100 [thread overview]
Message-ID: <CA+s+GJB+qvYBhjzvut2WJCeVc35nmwwUwQM45w_6BYwbw2UawA@mail.gmail.com> (raw)
In-Reply-To: <1387190808.12225.60115997.547B23B6@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Mon, Dec 16, 2013 at 11:46 AM, Jim <jim618@fastmail•co.uk> wrote:
> For the HD version of MultiBit we are removing the import
> of individual private keys entirely and only supporting HD
> addresses, primarily for safety reasons.
>
I'd love to have the same in Bitcoin-Qt as well. Too many sob stories about
people with outdated backups that lost part or all of their coins. These
are much more common than fee messups.
What we should really do is:
- Use deterministic wallets. Making regular backups becomes optional (to
retain label and transaction data and such) instead of mandatory.
- Don't support importing private keys. Replace the importing of private
keys by a "sweep" function.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1161 bytes --]
next prev parent reply other threads:[~2013-12-16 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 10:13 Drak
2013-12-16 10:46 ` Jim
2013-12-16 11:08 ` Drak
2013-12-16 11:31 ` Pieter Wuille
2013-12-16 18:26 ` Mike Hearn
2013-12-16 11:37 ` Wladimir [this message]
2013-12-16 17:55 ` Taylor Gerring
2013-12-16 18:45 ` Gregory Maxwell
2013-12-16 11:27 ` Wladimir
2013-12-16 18:28 ` Mike Hearn
2013-12-16 22:32 ` Andreas Schildbach
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=CA+s+GJB+qvYBhjzvut2WJCeVc35nmwwUwQM45w_6BYwbw2UawA@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jim618@fastmail$(echo .)co.uk \
/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