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
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
|
Return-Path: <earonesty@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
by lists.linuxfoundation.org (Postfix) with ESMTP id D341EC002A
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 12:50:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id AE7CC81E1B
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 12:50:17 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org AE7CC81E1B
Authentication-Results: smtp1.osuosl.org;
dkim=pass (2048-bit key) header.d=q32-com.20221208.gappssmtp.com
header.i=@q32-com.20221208.gappssmtp.com header.a=rsa-sha256
header.s=20221208 header.b=CUvXJEaY
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001,
HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=no autolearn_force=no
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id B5D9zPlFoQy1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 12:50:16 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 1819E81E17
Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com
[IPv6:2607:f8b0:4864:20::1133])
by smtp1.osuosl.org (Postfix) with ESMTPS id 1819E81E17
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 12:50:15 +0000 (UTC)
Received: by mail-yw1-x1133.google.com with SMTP id
00721157ae682-54f9e2d0714so7772967b3.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 09 May 2023 05:50:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=q32-com.20221208.gappssmtp.com; s=20221208; t=1683636615; x=1686228615;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:from:to:cc:subject:date:message-id:reply-to;
bh=LXj2UumHwEuaxJyMUnL4RdNxnonWjPTuvmOaolcT3xQ=;
b=CUvXJEaYY8Y5sSIfSyTUCw02FVXaDTM1koyfJK/A223wxxIVoOX3PDnPm+7rldxXJb
/81JoaGJqE8F0mLg2fLt96ovZxAh5dTkkkIALgEVQaELmuQouax1awnj1jAMuhCVmou0
9DyCQSZ2TQiMJas8FE3aamBBTlxiuuYUp9BVMn5vKfxoWcyyf4yYwHm4CFUR1NKGQUFd
3hn4hiP24Qhh7owQRVcu7KC9ogn2L/nAoYUmYdcH4EV55jfbfPvv797vLXnxYv7u/19a
iV1tdPJCZgiv8SVRdtvdXKGdTA41ARwjVrdQPak9TGSxAiSX3y8il4IDvCLby0ZxKcHj
oDPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20221208; t=1683636615; x=1686228615;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=LXj2UumHwEuaxJyMUnL4RdNxnonWjPTuvmOaolcT3xQ=;
b=dD466UFdcYvjwfbivKVDc+AAeN/CoBRA/h0aP1TMtpWFyr+1VBUtNoKPEn/jNxLBPM
D/9jOU3UzmVoym5W1ifI7PP/VGtugO44Sg33HJ7e/QwwygNhl5B/FgJhXZKVpp+Igz4/
DUHuc/iHfZSIF3AQaJMVq2WkqbqzrKcA2S3NkF9c86tlbwkOi3LqXMi9GFUSrAwb8yP/
4pemPRKdG7rrmzcbz7VA8sA2CsE69FKGz5nnWBoLR1jmgRVSI4p+Rue09s8VPPOb4+ZB
VeQtc5gCpHOaQr35YY+C/uegwHG+9JtUC6yH/N66vjk23c/H7yNG5jOwHGCI9+vey6Bz
mGXQ==
X-Gm-Message-State: AC+VfDw6jx9YOYaWSuLX6o33t8Yzo4QU6WA39Cd2H8ir+q133hVT5eCA
BJ0nMOc0/4EKFsafs7lkKAfJ31a6VMig1BtqRJckO9n2HlOf
X-Google-Smtp-Source: ACHHUZ6PJHljdYO2OkoybIppZyvpWlkvhCmN9NlqDe27pg+ByHtnJzpYJLouQywzXBEJXkq/wv45otjk7sDRPY7ycd0=
X-Received: by 2002:a81:1d07:0:b0:55d:7fd0:e3b9 with SMTP id
d7-20020a811d07000000b0055d7fd0e3b9mr14389117ywd.1.1683636614743; Tue, 09 May
2023 05:50:14 -0700 (PDT)
MIME-Version: 1.0
References: <183080646-e0c2bb9eaf62640f6c5d6c34f66db1d9@pmq7v.m5r2.onet>
In-Reply-To: <183080646-e0c2bb9eaf62640f6c5d6c34f66db1d9@pmq7v.m5r2.onet>
From: Erik Aronesty <erik@q32.com>
Date: Tue, 9 May 2023 08:50:03 -0400
Message-ID: <CAJowKgJVAfDiwUEy+6f1Ln45=mua=R7c=KxV5XZOJHvgEHsQhg@mail.gmail.com>
To: jk_14@op.pl,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000005a4eaf05fb423276"
X-Mailman-Approved-At: Tue, 09 May 2023 12:51:24 +0000
Subject: Re: [bitcoin-dev] [Mempool spam] Should we as developers reject
non-standard Taproot transactions from full nodes?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol 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: Tue, 09 May 2023 12:50:18 -0000
--0000000000005a4eaf05fb423276
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I would like to point out that I'm not an advocate for doing anything at
this point aside from working on l2
just to make it inconvenient for people
I just think the discussion of outputs and fees is interesting and related
to the game theory portion of Bitcoin
On Tue, May 9, 2023, 8:23 AM Jaroslaw via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>
> Ok, I need to highlight one important thing well proven by this discussio=
n
> (like it or not)...
>
> Not the spam itself is the real reason of feeling: "something must be don=
e"
> The reason is: $30 fee per transaction (I hope you all agree)
>
>
> Let me paraphrase some quotes used in this discussion, then:
>
> 1. Lack of block subsidy long term and necessity of $40 tx fee to
> compensate it - "threaten the smooth and normal use of the Bitcoin networ=
k
> as a peer-to-pear digital currency, as it was intended to be used as."
>
> 2. "the harmony of Bitcoin transactions is being disrupted right now" due
> to lack of block subsidy and due to exorbitant $40 tx fees as an effect
> necessary to keep the network security untouched
>
> 3. "Fee spikes aren't fun" and it's obvious that keeping the network
> security only on enormous tx fees of active users and having passive user=
s
> as free-riders - isn't fun, too
>
> 4. by ignoring Bitcoin long-term security budget problem - "we indirectly
> allowed this to happen, which previously wasn't possible before. So we al=
so
> have a responsibility to do something to ensure that this kind of
> tremendous $40 tx fees can never happen again"
>
> 5. "Action against exorbitant fees should have been taken months ago.
> (...) It's a mistake that the" tail emission or other necessary solution =
-
> weren't implemented on time
>
> 6. "we need to find a solution for long-term horrible fees problem - that
> fits everyone's common ground."
>
>
> Yes, we need - instead of being still in a heavy denial state.
>
> No additional comment then, except this little one:
> Delay of halving in case of 4 years long network difficulty regression
> situation.
>
>
> Regards,
> Jaroslaw
>
>
>
>
>
> W dniu 2023-05-09 00:37:57 u=C5=BCytkownik Luke Dashjr via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> napisa=C5=82:
>
> Action should have been taken months ago. Spam filtration has been a
> standard part of Bitcoin Core since day 1. It's a mistake that the existi=
ng
> filters weren't extended to Taproot transactions. We can address that, or
> try a more narrow approach like OP_RETURN (ie, what "Ordisrespector" does=
).
> Since this is a bugfix, it doesn't really even need to wait for a major
> release.
>
> (We already have pruning. It's not an alternative to spam filtering.)
>
> Luke
>
>
>
>
> On 5/7/23 13:22, Ali Sherief via bitcoin-dev wrote:
> Hi guys,
>
>
> I think everyone on this list knows what has happened to the Bitcoin
> mempool during the past 96 hours. Due to side projects such as BRC-20
> having such a high volume, real bitcoin transactions are being priced out
> and that is what is causing the massive congestion that has arguable not
> been seen since December 2017. I do not count the March 2021 congestion
> because that was only with 1-5sat/vbyte.
>
>
> Such justifiably worthless ("worthless" is not even my word - that's how
> its creator described them[1]) tokens threaten the smooth and normal use =
of
> the Bitcoin network as a peer-to-pear digital currency, as it was intende=
d
> to be used as.
>
>
> If the volume does not die down over the next few weeks, should we take a=
n
> action? The bitcoin network is a triumvirate of developers, miners, and
> users. Considering that miners are largely the entities at fault for
> allowing the system to be abused like this, the harmony of Bitcoin
> transactions is being disrupted right now. Although this community has a
> strong history of not putting its fingers into pies unless absolutely
> necessary - an example being during the block size wars and Segwit - shou=
ld
> similar action be taken now, in the form of i) BIPs and/or ii) commits in=
to
> the Bitcoin Core codebase, to curtail the loophole in BIP 342 (which
> defines the validation rules for Taproot scripts) which has allowed these
> unintended consequences?
>
>
> An alternative would be to enforce this "censorship" at the node level an=
d
> introduce a run-time option to instantly prune all non-standard Taproot
> transactions. This will be easier to implement, but won't hit the road
> until minimum next release.
>
>
> I know that some people will have their criticisms about this,
> absolutists/libertarians/maximum-freedom advocates, which is fine, but we
> need to find a solution for this that fits everyone's common ground. We
> indirectly allowed this to happen, which previously wasn't possible befor=
e.
> So we also have a responsibility to do something to ensure that this kind
> of congestion can never happen again using Taproot.
>
>
> -Ali
>
>
> ---
>
>
> [1]:
> https://www.coindesk.com/consensus-magazine/2023/05/05/pump-the-brcs-the-=
promise-and-peril-of-bitcoin-backed-tokens/
>
>
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--0000000000005a4eaf05fb423276
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">I would like to point out that I'm not an advocate fo=
r doing anything at this point aside from working on l2<div dir=3D"auto"><b=
r></div><div dir=3D"auto">just to make it inconvenient for people</div><div=
dir=3D"auto"><br></div><div dir=3D"auto">I just think the discussion of ou=
tputs and fees is interesting and related to the game theory portion of Bit=
coin</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, M=
ay 9, 2023, 8:23 AM Jaroslaw via bitcoin-dev <<a href=3D"mailto:bitcoin-=
dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>>=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Ok, I need to highlight one important thing well proven by this discussion =
(like it or not)...<br>
<br>
Not the spam itself is the real reason of feeling: "something must be =
done"<br>
The reason is: $30 fee per transaction (I hope you all agree)<br>
<br>
<br>
Let me paraphrase some quotes used in this discussion, then:<br>
<br>
1. Lack of block subsidy long term and necessity of $40 tx fee to compensat=
e it - "threaten the smooth and normal use of the Bitcoin network as a=
peer-to-pear digital currency, as it was intended to be used as."<br>
<br>
2. "the harmony of Bitcoin transactions is being disrupted right now&q=
uot; due to lack of block subsidy and due to exorbitant $40 tx fees as an e=
ffect necessary to keep the network security untouched<br>
<br>
3. "Fee spikes aren't fun" and it's obvious that keeping =
the network security only on enormous tx fees of active users and having pa=
ssive users as free-riders - isn't fun, too<br>
<br>
4. by ignoring Bitcoin long-term security budget problem - "we indirec=
tly allowed this to happen, which previously wasn't possible before. So=
we also have a responsibility to do something to ensure that this kind of =
tremendous $40 tx fees can never happen again"<br>
<br>
5. "Action against exorbitant fees should have been taken months ago. =
(...) It's a mistake that the" tail emission or other necessary so=
lution - weren't implemented on time<br>
<br>
6. "we need to find a solution for long-term horrible fees problem - t=
hat fits everyone's common ground."<br>
<br>
<br>
Yes, we need - instead of being still in a heavy denial state.<br>
<br>
No additional comment then, except this little one:<br>
Delay of halving in case of 4 years long network difficulty regression situ=
ation.<br>
<br>
<br>
Regards,<br>
Jaroslaw<br>
<br>
<br>
<br>
<br>
<br>
W dniu 2023-05-09 00:37:57 u=C5=BCytkownik Luke Dashjr via bitcoin-dev <=
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a>> napisa=C5=
=82:<br>
<br>
Action should have been taken months ago. Spam filtration has been a standa=
rd part of Bitcoin Core since day 1. It's a mistake that the existing f=
ilters weren't extended to Taproot transactions. We can address that, o=
r try a more narrow approach like OP_RETURN (ie, what "Ordisrespector&=
quot; does). Since this is a bugfix, it doesn't really even need to wai=
t for a major release.<br>
<br>
(We already have pruning. It's not an alternative to spam filtering.)<b=
r>
<br>
Luke<br>
<br>
<br>
<br>
<br>
On 5/7/23 13:22, Ali Sherief via bitcoin-dev wrote:<br>
Hi guys,<br>
<br>
<br>
I think everyone on this list knows what has happened to the Bitcoin mempoo=
l during the past 96 hours. Due to side projects such as BRC-20 having such=
a high volume, real bitcoin transactions are being priced out and that is =
what is causing the massive congestion that has arguable not been seen sinc=
e December 2017. I do not count the March 2021 congestion because that was =
only with 1-5sat/vbyte.<br>
<br>
<br>
Such justifiably worthless ("worthless" is not even my word - tha=
t's how its creator described them[1]) tokens threaten the smooth and n=
ormal use of the Bitcoin network as a peer-to-pear digital currency, as it =
was intended to be used as.<br>
<br>
<br>
If the volume does not die down over the next few weeks, should we take an =
action? The bitcoin network is a triumvirate of developers, miners, and use=
rs. Considering that miners are largely the entities at fault for allowing =
the system to be abused like this, the harmony of Bitcoin transactions is b=
eing disrupted right now. Although this community has a strong history of n=
ot putting its fingers into pies unless absolutely necessary - an example b=
eing during the block size wars and Segwit - should similar action be taken=
now, in the form of i) BIPs and/or ii) commits into the Bitcoin Core codeb=
ase, to curtail the loophole in BIP 342 (which defines the validation rules=
for Taproot scripts) which has allowed these unintended consequences?<br>
<br>
<br>
An alternative would be to enforce this "censorship" at the node =
level and introduce a run-time option to instantly prune all non-standard T=
aproot transactions. This will be easier to implement, but won't hit th=
e road until minimum next release.<br>
<br>
<br>
I know that some people will have their criticisms about this, absolutists/=
libertarians/maximum-freedom advocates, which is fine, but we need to find =
a solution for this that fits everyone's common ground. We indirectly a=
llowed this to happen, which previously wasn't possible before. So we a=
lso have a responsibility to do something to ensure that this kind of conge=
stion can never happen again using Taproot.<br>
<br>
<br>
-Ali<br>
<br>
<br>
---<br>
<br>
<br>
[1]:=C2=A0<a href=3D"https://www.coindesk.com/consensus-magazine/2023/05/05=
/pump-the-brcs-the-promise-and-peril-of-bitcoin-backed-tokens/" rel=3D"nore=
ferrer noreferrer" target=3D"_blank">https://www.coindesk.com/consensus-mag=
azine/2023/05/05/pump-the-brcs-the-promise-and-peril-of-bitcoin-backed-toke=
ns/</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--0000000000005a4eaf05fb423276--
|