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
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 82CF8B19
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 3 Mar 2016 15:36:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f52.google.com (mail-vk0-f52.google.com
[209.85.213.52])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AB4C5109
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 3 Mar 2016 15:36:50 +0000 (UTC)
Received: by mail-vk0-f52.google.com with SMTP id e185so25101770vkb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 03 Mar 2016 07:36:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc; bh=op6Zu6VVMGDnhzzroQq5wfhyXXPp0EnIc/ANaCLZL9s=;
b=thjvsdPACe3+CnfkLrBwb91Z2W48uo8KH+AEHjNI929RVtMcM5sbr2Dj52R9xrViiq
617b0df9YVC9mPIzb7yDbnZuFi3XHAM8Vp1HaOw4594aqoMGkTW4v/YuIkP7InUrS380
SmKtIyMa4/czyEJ8IrfvNF2rM/VUzl1hvAOI80vOYMkijfZh1l20+U1Sb2iZ5EU5XVKu
2xuqnTGrefEEf6gRwUFfk4AeAeGzkJP0BSATETLFAxRQ76JpJTf9i0aifLB6swMaigO6
RoCkkCOS0brr7Ia0AktkySowSyTaoawlnu4ZjRw5LHerXLW8E0hScbuYpzclxHJ44noS
POPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc;
bh=op6Zu6VVMGDnhzzroQq5wfhyXXPp0EnIc/ANaCLZL9s=;
b=J7uQgxVboIvUXlMGIfC3lBDVDUgSmuuS+kX2pNgXeJCYCQLu4xCJpMQblIyXxG3uHc
hRPgeWKvRwjQeF5dqyhXpGv7b1rN3tR3aqj2+d5bV5dmXUrrvwd13kKX9r3qVEmG1D4W
7JDLG3e9hq0NVmAB+/fMZOEgKAVdOzR6u1btuk/mFdFaI3TQxCE83fzAvvE7uTbMLnjN
IkBnHnq4b29kaQiKhPgBfcsNu08s7oPEvQOUGAsQ4LChq6ulhk74wwSeX3qAJ699gZS7
ONjLXsl/Ujf0wP4BX8aIH34lgzvBeO97r0AyRDtX4T5DffBkf9ttXzJvMzmTP68y5hi7
bucQ==
X-Gm-Message-State: AD7BkJLYGPnF/sYl1mwKniqWzREh+67M34f3LEZG36+Prt2tvLXc4YLeIGFO54g/9/rApSlf9kcpMFlzx6YBCA==
MIME-Version: 1.0
X-Received: by 10.31.154.21 with SMTP id c21mr2414962vke.38.1457019409917;
Thu, 03 Mar 2016 07:36:49 -0800 (PST)
Received: by 10.31.141.73 with HTTP; Thu, 3 Mar 2016 07:36:48 -0800 (PST)
Received: by 10.31.141.73 with HTTP; Thu, 3 Mar 2016 07:36:48 -0800 (PST)
In-Reply-To: <20160303150418.GA2341@banane.informatik.uni-ulm.de>
References: <56D835D3.9070902@librelamp.com>
<20160303150418.GA2341@banane.informatik.uni-ulm.de>
Date: Thu, 3 Mar 2016 16:36:48 +0100
Message-ID: <CABm2gDqbxAkZzfycEzX7370CAYMsyzL=L3tAKh6CNO4QOJyLsg@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Henning Kopp <henning.kopp@uni-ulm.de>
Content-Type: multipart/alternative; boundary=001a1140ed445c1153052d26c472
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 03 Mar 2016 15:37:52 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] consensus rule change for TX fee safety
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2016 15:36:51 -0000
--001a1140ed445c1153052d26c472
Content-Type: text/plain; charset=UTF-8
There's an absurd fee (non-consensus) check already. Maybe that check can
be improved, but probably the wallet layer is more appropriate for this.
On Mar 3, 2016 16:23, "Henning Kopp via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi,
> I think there is no need to do a hardfork for this. Rather it should
> be implemented as a safety-mechanism in the client. Perhaps a warning
> can pop up, if one of your conditions A) or B) is met.
>
> All the best
> Henning Kopp
>
>
> On Thu, Mar 03, 2016 at 05:02:11AM -0800, Alice Wonder via bitcoin-dev
> wrote:
> > I think the next hard fork should require a safety rule for TX fees.
> >
> >
> https://blockchain.info/tx/6fe69404e6c12b25b60fcd56cc6dc9fb169b24608943def6dbe1eb0a9388ed08
> >
> > 15 BTC TX fee for < 7 BTC of outputs.
> >
> > Probably either a typo or client bug.
> >
> > My guess is the user was using a client that does not adjust TX fee, and
> > needed to manually set it in order to get the TX in the block sooner, and
> > meant 15 mBTC or something.
> >
> > I suggest that either :
> >
> > A) TX fee may not be larger than sum of outputs
> > B) TX fee per byte may not be larger than 4X largest fee per byte in
> > previous block
> >
> > Either of those would have prevented this TX from going into a block.
> >
> > Many people I know are scared of bitcoin, that they will make a TX and
> make
> > a mistake they can't undo.
> >
> > Adding protections may help give confidence and there is precedence to
> doing
> > things to prevent typo blunders - a public address has a four byte
> checksum
> > to reduce the odds of a typo.
> >
> > This kind of mistake is rare, so a fix could be included in the coming HF
> > for the possible July 2017 block increase.
> >
> > Thank you for your time.
> >
> > Alice Wonder
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
>
> --
> Henning Kopp
> Institute of Distributed Systems
> Ulm University, Germany
>
> Office: O27 - 3402
> Phone: +49 731 50-24138
> Web: http://www.uni-ulm.de/in/vs/~kopp
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a1140ed445c1153052d26c472
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">There's=C2=A0 an absurd fee (non-consensus) check alread=
y. Maybe that check can be improved, but probably the wallet layer is more =
appropriate for this.</p>
<div class=3D"gmail_quote">On Mar 3, 2016 16:23, "Henning Kopp via bit=
coin-dev" <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org"=
>bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br type=3D"attributio=
n"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">Hi,<br>
I think there is no need to do a hardfork for this. Rather it should<br>
be implemented as a safety-mechanism in the client. Perhaps a warning<br>
can pop up, if one of your conditions A) or B) is met.<br>
<br>
All the best<br>
Henning Kopp<br>
<br>
<br>
On Thu, Mar 03, 2016 at 05:02:11AM -0800, Alice Wonder via bitcoin-dev wrot=
e:<br>
> I think the next hard fork should require a safety rule for TX fees.<b=
r>
><br>
> <a href=3D"https://blockchain.info/tx/6fe69404e6c12b25b60fcd56cc6dc9fb=
169b24608943def6dbe1eb0a9388ed08" rel=3D"noreferrer" target=3D"_blank">http=
s://blockchain.info/tx/6fe69404e6c12b25b60fcd56cc6dc9fb169b24608943def6dbe1=
eb0a9388ed08</a><br>
><br>
> 15 BTC TX fee for < 7 BTC of outputs.<br>
><br>
> Probably either a typo or client bug.<br>
><br>
> My guess is the user was using a client that does not adjust TX fee, a=
nd<br>
> needed to manually set it in order to get the TX in the block sooner, =
and<br>
> meant 15 mBTC or something.<br>
><br>
> I suggest that either :<br>
><br>
> A) TX fee may not be larger than sum of outputs<br>
> B) TX fee per byte may not be larger than 4X largest fee per byte in<b=
r>
> previous block<br>
><br>
> Either of those would have prevented this TX from going into a block.<=
br>
><br>
> Many people I know are scared of bitcoin, that they will make a TX and=
make<br>
> a mistake they can't undo.<br>
><br>
> Adding protections may help give confidence and there is precedence to=
doing<br>
> things to prevent typo blunders - a public address has a four byte che=
cksum<br>
> to reduce the odds of a typo.<br>
><br>
> This kind of mistake is rare, so a fix could be included in the coming=
HF<br>
> for the possible July 2017 block increase.<br>
><br>
> Thank you for your time.<br>
><br>
> Alice Wonder<br>
> _______________________________________________<br>
> bitcoin-dev mailing list<br>
> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a><br>
> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
><br>
<br>
--<br>
Henning Kopp<br>
Institute of Distributed Systems<br>
Ulm University, Germany<br>
<br>
Office: O27 - 3402<br>
Phone: <a href=3D"tel:%2B49%20731%2050-24138" value=3D"+497315024138">+49 7=
31 50-24138</a><br>
Web: <a href=3D"http://www.uni-ulm.de/in/vs/~kopp" rel=3D"noreferrer" targe=
t=3D"_blank">http://www.uni-ulm.de/in/vs/~kopp</a><br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--001a1140ed445c1153052d26c472--
|
