1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <drak@zikula.org>) id 1VsVBP-0004Q8-92
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Dec 2013 10:13:51 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of zikula.org
designates 74.125.82.43 as permitted sender)
client-ip=74.125.82.43; envelope-from=drak@zikula.org;
helo=mail-wg0-f43.google.com;
Received: from mail-wg0-f43.google.com ([74.125.82.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VsVBO-0004A1-7q
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Dec 2013 10:13:51 +0000
Received: by mail-wg0-f43.google.com with SMTP id k14so4389387wgh.10
for <bitcoin-development@lists.sourceforge.net>;
Mon, 16 Dec 2013 02:13:43 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to
:content-type;
bh=c4QWpG20vAw8HB5XlIngNwVJVhkGE2zJm6nNcKdpY10=;
b=j0TZ6jtcXxOOwgDR749UO8Pz+EX422qjtFvPE9kgjqCG8omzacMVAjjVJjoG3+dvMr
U+fGrwWiZFpyHKbbXjcV5zOSSQnrTchyYK/FJWdTWU9SfllZKOjJFO3KoaAATj4vFq1+
FdoDgo48kt+WV8EBbQ4BwyllOmEovWxagjSL3ue6MhEQ2+PWqTnaL5651mxtilTnngY1
nO9b4pAnC8WyNkAp4e/d1Y6MnfN10tV8FUWt3oJXR9EFLQ9cCQJGvX7Gq2di3jA81h/G
nmVrH2O6UlLMps+LtSgPPMBeLD7RVZeX8B/loxYDxkxpKCVlb6zikFA++D9fVBlvu3PF
C4HA==
X-Gm-Message-State: ALoCoQn+Y/ui5Wnt9/COKHVwfWFnp9Aq8Us4TgaygGQqYInZsB/K1/RdTRsMDOxPlPmM6RAU7DyQ
X-Received: by 10.180.108.162 with SMTP id hl2mr12470905wib.56.1387188823781;
Mon, 16 Dec 2013 02:13:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.93.105 with HTTP; Mon, 16 Dec 2013 02:13:22 -0800 (PST)
From: Drak <drak@zikula.org>
Date: Mon, 16 Dec 2013 10:13:22 +0000
Message-ID: <CANAnSg0QnZQ2BNJRYm1SD4HePZJQZy3GuAejLXYH+rLFn34CtA@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=e89a8f3bac6f1410ca04eda4111b
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: reddit.com]
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VsVBO-0004A1-7q
Subject: [Bitcoin-development] Fees UI warning
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 16 Dec 2013 10:13:51 -0000
--e89a8f3bac6f1410ca04eda4111b
Content-Type: text/plain; charset=UTF-8
Not sure if this is the right place, but since a few wallet authors
congregate here I though it might be the best place.
It seems every once in a while you see stories of people accidentally
paying huge fees. Today I read about a man who paid a 20.14BTC fee for a
0.05 BTC transaction[1], oops. There was another recently where someone
paid a fee of about 200BTC which fortunately the pool operator refunded.
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. "the fee seems unusually high, are you really sure you
want to pay X in fees?"
I realise the exact details of this might need to be fleshed out given we
want flexible fees, but it should be pretty simple to agree with what looks
like an unusually large fee according to the going rate.
Drak
[1]
http://www.reddit.com/r/Bitcoin/comments/1syu3h/i_lost_all_my_bitcoins_in_an_erroneous/
--e89a8f3bac6f1410ca04eda4111b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Not sure if this is the right place, but since a few walle=
t authors congregate here I though it might be the best place.<div><br></di=
v><div>It seems every once in a while you see stories of people accidentall=
y paying huge fees. Today I read about a man who paid a 20.14BTC fee for a =
0.05 BTC transaction[1], oops. There was another recently where someone pai=
d a fee of about 200BTC which fortunately the pool operator refunded.</div>
<div><br></div><div>It just occurs to me this kind of sad story could be av=
erted if wallets implemented a confirmation box if the fee amount seems cra=
zy - for example, if it's >10x what the default fee should be, or if=
it's greater than x% of the sending amount. "the fee seems unusua=
lly high, are you really sure you want to pay X in fees?"</div>
<div><br></div><div>I realise the exact details of this might need to be fl=
eshed out given we want flexible fees, but it should be pretty simple to ag=
ree with what looks like an unusually large fee according to the going rate=
.</div>
<div><br></div><div>Drak<br></div><div><br></div><div>[1]=C2=A0<a href=3D"h=
ttp://www.reddit.com/r/Bitcoin/comments/1syu3h/i_lost_all_my_bitcoins_in_an=
_erroneous/">http://www.reddit.com/r/Bitcoin/comments/1syu3h/i_lost_all_my_=
bitcoins_in_an_erroneous/</a>=C2=A0</div>
</div>
--e89a8f3bac6f1410ca04eda4111b--
|
