From: Mike Hearn <mike@plan99•net>
To: Drak <drak@zikula•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fees UI warning
Date: Mon, 16 Dec 2013 19:28:08 +0100 [thread overview]
Message-ID: <CANEZrP1Fm2cEEXNih7arWoLPNEU4d=y0QZxqi30q+n0wh9nV-w@mail.gmail.com> (raw)
In-Reply-To: <CANAnSg0QnZQ2BNJRYm1SD4HePZJQZy3GuAejLXYH+rLFn34CtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Mon, Dec 16, 2013 at 11:13 AM, Drak <drak@zikula•org> wrote:
> It just occurs to me this kind of sad story could be averted if wallets
> implemented a confirmation box if the fee amount seems crazy - for example,
> if it's >10x what the default fee should be, or if it's greater than x% of
> the sending amount.
>
Most good wallets have UI's designed to be safe. Unfortunately this guy was
using brainwallet.org which is by no means a "good" wallet in that sense
(it's not really even a wallet app at all)
I think most of us have expressed displeasure at the existence of this site
before, and I once even asked the guy to stop running it, but he refused.
It's an extremely sharp tool which makes it easy to cut yourself, except it
doesn't look dangerous, it looks like ordinary software designed for
ordinary people.
I don't know how to solve this. Badly designed software that looks
appealing will always be a danger.
[-- Attachment #2: Type: text/html, Size: 1396 bytes --]
next prev parent reply other threads:[~2013-12-16 18:28 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
2013-12-16 11:27 ` Wladimir
2013-12-16 18:28 ` Mike Hearn [this message]
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='CANEZrP1Fm2cEEXNih7arWoLPNEU4d=y0QZxqi30q+n0wh9nV-w@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=drak@zikula$(echo .)org \
/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