From: Gregory Maxwell <gmaxwell@gmail•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fees UI warning
Date: Mon, 16 Dec 2013 10:45:57 -0800 [thread overview]
Message-ID: <CAAS2fgRLWLgOvZLA3NUgnqrHz=mSUNU3y9GJbPdyZNAfRS3=qQ@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJB+qvYBhjzvut2WJCeVc35nmwwUwQM45w_6BYwbw2UawA@mail.gmail.com>
On Mon, Dec 16, 2013 at 3:37 AM, Wladimir <laanwj@gmail•com> wrote:
> 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.
I'd add a third: make structured key-management possible, e.g.
At a minimum: Users should be able to hit a "retire keys / keys
possibly compromised" button, which creates a new seed, forces the
user to make a backup (and allows more than one), then switches to the
new seed and moves all their coins.
On Mon, Dec 16, 2013 at 10:28 AM, Mike Hearn <mike@plan99•net> wrote:
> I don't know how to solve this. Badly designed software that looks appealing
> will always be a danger.
"We didn't say it couldn't be done— We said don't do it!"
Part of the challenge here is that the service does a number of things
people _really_ shouldn't be doing— things so dangerous that I
certainly won't do them— and as a result to not use the site turn into
big education efforts rather than just "use this other thing (that
also does the wrong headed thing you want to do)".
next prev parent reply other threads:[~2013-12-16 18:46 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
2013-12-16 17:55 ` Taylor Gerring
2013-12-16 18:45 ` Gregory Maxwell [this message]
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='CAAS2fgRLWLgOvZLA3NUgnqrHz=mSUNU3y9GJbPdyZNAfRS3=qQ@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@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