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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1VsWLE-0004To-L9
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Dec 2013 11:28:04 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.54 as permitted sender)
client-ip=209.85.214.54; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f54.google.com;
Received: from mail-bk0-f54.google.com ([209.85.214.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VsWLA-0001Hx-LL
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Dec 2013 11:28:04 +0000
Received: by mail-bk0-f54.google.com with SMTP id v16so2256081bkz.41
for <bitcoin-development@lists.sourceforge.net>;
Mon, 16 Dec 2013 03:27:54 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.205.9.131 with SMTP id ow3mr155028bkb.152.1387193274206;
Mon, 16 Dec 2013 03:27:54 -0800 (PST)
Received: by 10.204.69.197 with HTTP; Mon, 16 Dec 2013 03:27:54 -0800 (PST)
In-Reply-To: <CANAnSg0QnZQ2BNJRYm1SD4HePZJQZy3GuAejLXYH+rLFn34CtA@mail.gmail.com>
References: <CANAnSg0QnZQ2BNJRYm1SD4HePZJQZy3GuAejLXYH+rLFn34CtA@mail.gmail.com>
Date: Mon, 16 Dec 2013 12:27:54 +0100
Message-ID: <CA+s+GJApRy+Y7bqWPNoQ3O1FooM0T1sBB2_jwzOg51q4Oc1RBg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Drak <drak@zikula.org>
Content-Type: multipart/alternative; boundary=20cf3022380758384c04eda51af1
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-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: zikula.org]
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VsWLA-0001Hx-LL
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [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 11:28:04 -0000
--20cf3022380758384c04eda51af1
Content-Type: text/plain; charset=UTF-8
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. "the fee seems unusually high, are you really sure you
> want to pay X in fees?"
>
Bitcoin-qt (in master) always shows the fee and total amount that is going
to be paid in the confirmation dialog, so it is very hard to accidentally a
very high fee.
Wladimir
--20cf3022380758384c04eda51af1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Dec 16, 2013 at 11:13 AM, Drak <span dir=3D"ltr"><<a href=3D"mailto:=
drak@zikula.org" target=3D"_blank">drak@zikula.org</a>></span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div>It just occurs to me this kind of sad story could be =
averted if wallets implemented a confirmation box if the fee amount seems c=
razy - 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 unus=
ually high, are you really sure you want to pay X in fees?"</div>
</div></blockquote><div><br></div><div>Bitcoin-qt (in master) always shows =
the fee and total amount that is going to be paid in the confirmation dialo=
g, so it is very hard to accidentally a very high fee.</div><div><br></div>
<div>Wladimir</div><div><br></div></div></div></div>
--20cf3022380758384c04eda51af1--
|
