summaryrefslogtreecommitdiff
path: root/d7/d518ef7166517e9ff82c2bfabae45d66e02502
blob: bbebfc04382ecf166c28200331e1676ed1fbaa44 (plain)
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
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
Return-Path: <tomh@thinlink.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 8D3CCC002A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 May 2023 15:21:51 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 6F16F4038D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 May 2023 15:21:51 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 6F16F4038D
Authentication-Results: smtp2.osuosl.org;
 dkim=pass (2048-bit key) header.d=thinlink-com.20221208.gappssmtp.com
 header.i=@thinlink-com.20221208.gappssmtp.com header.a=rsa-sha256
 header.s=20221208 header.b=Rqatk45J
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id F-J-TYF7fc1B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 May 2023 15:21:50 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org A64054012D
Received: from mail-yw1-x112b.google.com (mail-yw1-x112b.google.com
 [IPv6:2607:f8b0:4864:20::112b])
 by smtp2.osuosl.org (Postfix) with ESMTPS id A64054012D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  9 May 2023 15:21:49 +0000 (UTC)
Received: by mail-yw1-x112b.google.com with SMTP id
 00721157ae682-559e317eef1so88655877b3.0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 09 May 2023 08:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=thinlink-com.20221208.gappssmtp.com; s=20221208; t=1683645708; x=1686237708; 
 h=in-reply-to:from:references:to:content-language:subject:user-agent
 :mime-version:date:message-id:from:to:cc:subject:date:message-id
 :reply-to; bh=hqezPSCE3u6zFx/VuWZA4uRoxtNqz7a/vDY35s0e9HE=;
 b=Rqatk45Jtd9w8qYRrmlonXgarPOFjGV86oftrEKwhawQbLg/taFPbFnJiqv3ivSNl6
 Fc6qKlI4eBJunBFcvLgKQkH6wyyIiD9okk8J2AGwhaNiggJuKemvyM8s7ZUtJnjV5hAM
 PgOf/DxQdZ4iSXz/tsGFLNAg4ViIFmgLLW0kaGLze0L774fAKeb+sUVV6UngVti4N+9w
 z+r5cVD7iMbG8Mq73pvrAr/73vBn1n4ugZC0YUpZBYqzN8/AxGB8HTb4uPzbHB4SHM67
 3V1Odv/Ws/P5qg5FF++K131quUEg4QG4pCYzxZWdUxqNKn22INcxnilt1KV3yLknQGm+
 BdDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1683645708; x=1686237708;
 h=in-reply-to:from:references:to:content-language:subject:user-agent
 :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject
 :date:message-id:reply-to;
 bh=hqezPSCE3u6zFx/VuWZA4uRoxtNqz7a/vDY35s0e9HE=;
 b=PJvf/9xkQOx54I37w1nIOVwVhuL+xnH9MNBm9UWb0j8sn1gB1LkiTtUDjrse81zrnK
 1ouZkGfzPwvhTVqTFU/OPEy0d9QN8YQjy7cEHUHCda/+WkEu3bAEZQrDsn09oZ0Yit3H
 Qt6oOaP8bPKClHGKxRTSeks96J9SIrF6XIQo6DrjdOKngBrwJ2GT8/Gffn/t35TCpPMv
 tIG8yLbQiOO6nw4QBCCs+4DxmA+RWROhTxMFuTuuSuY43E4mqUUWYrSzApDJM+dgwa9p
 XUsEviT1efXWZzH7rMeZtoNsTF6irLSKcAmK+Xa6SnvJjKxyO9idAlVQWFGau8SoMoi7
 42aQ==
X-Gm-Message-State: AC+VfDx1XtwbJN49wf7FSX75hHK+41Q35TyDx9F84KtghY4FexSDtil6
 ds1MrihWfByZUNsHyEyd70AaLZJ9lKOy6aztxR8=
X-Google-Smtp-Source: ACHHUZ4EfnwFUaRyL4C1T55XXCqHKaTpKdYS6sbaP009SoRzfllweLnm6M461AqijVXipWTXXmhrcg==
X-Received: by 2002:a25:3297:0:b0:b8c:49c:85cf with SMTP id
 y145-20020a253297000000b00b8c049c85cfmr15241122yby.3.1683645708282; 
 Tue, 09 May 2023 08:21:48 -0700 (PDT)
Received: from ?IPV6:2600:1700:b950:d740:32f:2eb8:4f17:b8fe?
 ([2600:1700:b950:d740:32f:2eb8:4f17:b8fe])
 by smtp.gmail.com with ESMTPSA id
 2-20020a251202000000b00b9db62abff3sm3090803ybs.58.2023.05.09.08.21.47
 for <bitcoin-dev@lists.linuxfoundation.org>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Tue, 09 May 2023 08:21:47 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary="------------98CjMHj6Df9j6M4rcHr2hFZj"
Message-ID: <1b4db941-4c64-979e-9b3b-ea112aab9080@thinlink.com>
Date: Tue, 9 May 2023 08:21:46 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.0
Content-Language: en-US
To: bitcoin-dev@lists.linuxfoundation.org
References: <Lm_5F74G9G21ydrFPovvmtHWpNXcbVzZibmU80oNqFRehJjcll89-t7OXqS5Fooe0cTNxGreIREMql3Li2xUCe2T5NVyss3-CrLzISO09HY=@notatether.com>
 <CAJowKgJaG8ZnZMuVTSmyhMxZKb4pcMF1XM+WH8j64Gasoy1kcw@mail.gmail.com>
 <-2tdTjN6WfQI-CTPM49DiMOC2X5El1vJdlWTQvpalXAHKVLdFd_7ADpYN7Cz57v0fJSkaiG75fHJzcBtvJgn7Pj-RZrEk6hXk6Rp_1Y7SrE=@protonmail.com>
From: Tom Harding <tomh@thinlink.com>
In-Reply-To: <-2tdTjN6WfQI-CTPM49DiMOC2X5El1vJdlWTQvpalXAHKVLdFd_7ADpYN7Cz57v0fJSkaiG75fHJzcBtvJgn7Pj-RZrEk6hXk6Rp_1Y7SrE=@protonmail.com>
X-Mailman-Approved-At: Tue, 09 May 2023 16:18:39 +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 15:21:51 -0000

This is a multi-part message in MIME format.
--------------98CjMHj6Df9j6M4rcHr2hFZj
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

> And prevent perfectly reasonable transfers of value


Such a transfer can only be reasonable when off-chain value is attached 
to the coins.  A rule like this is the embodiment of the philosophy that 
the Bitcoin network is for onchain-economic transactions.

Parties could get around the rule by paying miners off-network, and that 
would be an appropriate penalty for using non-onchain-economic transactions.



On 5/8/23 10:13, Michael Folkson via bitcoin-dev wrote:
> > probably easier just to reject any transaction where the fee is 
> higher than the sum of the outputs
>
> And prevent perfectly reasonable transfers of value and attempted 
> Lightning channel closes during fee spikes? If I *want*​ to close my 
> Lightning channel during a protracted fee spike where I have to pay an 
> onchain transaction fee greater than the amount I am receiving you 
> want to stop me doing that? You are impinging on a valid use case as 
> well as requiring a consensus rule change.
>
> -- Michael Folkson
> Email: michaelfolkson at protonmail.com <http://protonmail.com/>
> GPG: A2CF5D71603C92010659818D2A75D601B23FEE0F
> Learn about Bitcoin: https://www.youtube.com/@portofbitcoin
>
> ------- Original Message -------
> On Monday, May 8th, 2023 at 13:58, Erik Aronesty via bitcoin-dev 
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> probably easier just to reject any transaction where the fee is 
>> higher than the sum of the outputs
>>
>>
>>
>> On Mon, May 8, 2023, 7:55 AM Ali Sherief via bitcoin-dev 
>> <bitcoin-dev@lists.linuxfoundation.org> 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 intended to be used as.
>>
>>     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 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 - should
>>     similar action be taken now, in the form of i) BIPs and/or ii)
>>     commits into 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 and 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 before. 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/
>>     <https://www.coindesk.com/consensus-magazine/2023/05/05/pump-the-brcs-the-promise-and-peril-of-bitcoin-backed-tokens/?outputType=amp>
>>     _______________________________________________
>>     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
--------------98CjMHj6Df9j6M4rcHr2hFZj
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body>
    <p>
      <blockquote type=3D"cite"><span style=3D"font-family:system-ui,
          sans-serif;display:inline !important">And prevent perfectly
          reasonable transfers of value</span></blockquote>
    </p>
    <p><br>
    </p>
    <p>Such a transfer can only be reasonable when off-chain value is
      attached to the coins.=C2=A0 A rule like this is the embodiment of =
the
      philosophy that the Bitcoin network is for onchain-economic
      transactions.<br>
    </p>
    <p>Parties could get around the rule by paying miners off-network,
      and that would be an appropriate penalty for using
      non-onchain-economic transactions.<br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <div class=3D"moz-cite-prefix">On 5/8/23 10:13, Michael Folkson via
      bitcoin-dev wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:-2tdTjN6WfQI-CTPM49DiMOC2X5El1vJdlWTQvpalXAHKVLdFd_7ADpYN7Cz5=
7v0fJSkaiG75fHJzcBtvJgn7Pj-RZrEk6hXk6Rp_1Y7SrE=3D@protonmail.com">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DU=
TF-8">
      <div style=3D"font-family: Arial, sans-serif; font-size: 14px;">&gt=
;=C2=A0<span
          style=3D"font-family:system-ui, sans-serif;display:inline
          !important">probably easier just to reject any transaction
          where the fee is higher than the sum of the outputs</span></div=
>
      <div style=3D"font-family: Arial, sans-serif; font-size: 14px;"><sp=
an
          style=3D"font-family:system-ui, sans-serif;display:inline
          !important"><br>
        </span></div>
      <div style=3D"font-family: Arial, sans-serif; font-size: 14px;"><sp=
an
          style=3D"font-family:system-ui, sans-serif;display:inline
          !important">And prevent perfectly reasonable transfers of
          value and attempted Lightning channel closes during fee
          spikes? If I <b>want</b>=E2=80=8B to close my Lightning channel=

          during a protracted fee spike where I have to pay an onchain
          transaction fee greater than the amount I am receiving you
          want to stop me doing that? You are impinging on a valid use
          case as well as requiring a consensus rule change.</span></div>=

      <div style=3D"font-family: Arial, sans-serif; font-size: 14px;"><sp=
an
          style=3D"font-family:system-ui, sans-serif;display:inline
          !important"><br>
        </span></div>
      <div class=3D"protonmail_signature_block" style=3D"font-family: Ari=
al,
        sans-serif; font-size: 14px;">
        <div class=3D"protonmail_signature_block-user">
          <div style=3D"font-family:arial;font-size:14px;"><span style=3D=
"color:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:nor=
mal;text-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing=
:0px;background-color:rgb(255,255,255);float:none;display:inline;"><span =
style=3D"font-family:'SFMono-Regular', Consolas, 'Liberation Mono', Menlo=
, monospace, monospace;" class=3D"font"><span style=3D"font-size:14px;" c=
lass=3D"size">--
Michael Folkson</span></span></span></div>
          <div style=3D"font-family:arial;font-size:14px;"><span style=3D=
"color:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:nor=
mal;text-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing=
:0px;background-color:rgb(255,255,255);float:none;display:inline;"><span =
style=3D"font-family:'SFMono-Regular', Consolas, 'Liberation Mono', Menlo=
, monospace, monospace;" class=3D"font"><span style=3D"font-size:14px;" c=
lass=3D"size">Email: michaelfolkson at </span></span></span><a href=3D"ht=
tp://protonmail.com/" style=3D"line-height:normal;text-decoration:underli=
ne;font-family:'SFMono-Regular', Consolas, 'Liberation Mono', Menlo, mono=
space, monospace;font-size:14px;font-style:normal;font-weight:400;letter-=
spacing:normal;text-indent:0px;text-transform:none;white-space:pre-wrap;w=
ord-spacing:0px;" rel=3D"noopener noreferrer" target=3D"_blank" moz-do-no=
t-send=3D"true">protonmail.com</a><span style=3D"color:rgb(38,42,51);font=
-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-=
transform:none;white-space:pre-wrap;word-spacing:0px;background-color:rgb=
(255,255,255);float:none;display:inline;"><span style=3D"font-family:'SFM=
ono-Regular', Consolas, 'Liberation Mono', Menlo, monospace, monospace;" =
class=3D"font"><span style=3D"font-size:14px;" class=3D"size"> </span></s=
pan></span></div>
          <div style=3D"font-family:arial;font-size:14px;"><span style=3D=
"color:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:nor=
mal;text-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing=
:0px;background-color:rgb(255,255,255);float:none;display:inline;"><span =
style=3D"font-family:'SFMono-Regular', Consolas, 'Liberation Mono', Menlo=
, monospace, monospace;" class=3D"font"><span style=3D"font-size:14px;" c=
lass=3D"size">GPG: <span>A2CF5D71603C92010659818D2A75D601B23FEE0F</span><=
/span></span></span></div>
          <div style=3D"font-family:arial;font-size:14px;"><span style=3D=
"color:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:nor=
mal;text-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing=
:0px;background-color:rgb(255,255,255);float:none;display:inline;"><span =
style=3D"font-family:'SFMono-Regular', Consolas, 'Liberation Mono', Menlo=
, monospace, monospace;" class=3D"font"><span style=3D"font-size:14px;" c=
lass=3D"size"><span>
</span></span></span></span></div>
          <div style=3D"font-family:arial;font-size:14px;"><span style=3D=
"color:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:nor=
mal;text-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing=
:0px;background-color:rgb(255,255,255);float:none;display:inline;"><span =
style=3D"font-family:'SFMono-Regular', Consolas, 'Liberation Mono', Menlo=
, monospace, monospace;" class=3D"font"><span style=3D"font-size:14px;" c=
lass=3D"size"><span>Learn about Bitcoin: <span><a href=3D"https://www.you=
tube.com/@portofbitcoin" rel=3D"noopener noreferrer" target=3D"_blank" mo=
z-do-not-send=3D"true" class=3D"moz-txt-link-freetext">https://www.youtub=
e.com/@portofbitcoin</a></span></span></span></span></span></div>
        </div>
        <div class=3D"protonmail_signature_block-proton
          protonmail_signature_block-empty"> </div>
      </div>
      <div style=3D"font-family: Arial, sans-serif; font-size: 14px;"><br=
>
      </div>
      <div class=3D"protonmail_quote"> ------- Original Message -------<b=
r>
        On Monday, May 8th, 2023 at 13:58, Erik Aronesty via bitcoin-dev
        <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:bitcoin-dev@lis=
ts.linuxfoundation.org">&lt;bitcoin-dev@lists.linuxfoundation.org&gt;</a>=
 wrote:<br>
        <br>
        <blockquote class=3D"protonmail_quote" type=3D"cite">
          <div dir=3D"auto">probably easier just to reject any transactio=
n
            where the fee is higher than the sum of the outputs
            <div dir=3D"auto"><br>
            </div>
            <div dir=3D"auto"><br>
            </div>
          </div>
          <br>
          <div class=3D"gmail_quote">
            <div class=3D"gmail_attr" dir=3D"ltr">On Mon, May 8, 2023, 7:=
55
              AM Ali Sherief via bitcoin-dev &lt;<a
                href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org"
                rel=3D"noreferrer nofollow noopener" target=3D"_blank"
                moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext">=
bitcoin-dev@lists.linuxfoundation.org</a>&gt;
              wrote:<br>
            </div>
            <blockquote style=3D"margin:0 0 0 .8ex;border-left:1px #ccc
              solid;padding-left:1ex" class=3D"gmail_quote">
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
Hi
                guys,</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
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.</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
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
                intended to be used as.</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
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 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 - should similar action be taken now, in the
                form of i) BIPs and/or ii) commits into 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?</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
An
                alternative would be to enforce this "censorship" at the
                node level and 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.</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
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 before. So we also have a responsibility
                to do something to ensure that this kind of congestion
                can never happen again using Taproot.</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
-Ali</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
---</div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
<br>
              </div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=
[1]:
                <span><a target=3D"_blank"
href=3D"https://www.coindesk.com/consensus-magazine/2023/05/05/pump-the-b=
rcs-the-promise-and-peril-of-bitcoin-backed-tokens/?outputType=3Damp"
                    rel=3D"noreferrer nofollow noopener"
                    moz-do-not-send=3D"true">https://www.coindesk.com/con=
sensus-magazine/2023/05/05/pump-the-brcs-the-promise-and-peril-of-bitcoin=
-backed-tokens/</a></span></div>
              <div style=3D"font-family:Arial,sans-serif;font-size:14px">=

                <div> </div>
                <div> </div>
              </div>
              _______________________________________________<br>
              bitcoin-dev mailing list<br>
              <a rel=3D"noreferrer nofollow noopener" target=3D"_blank"
                href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org"
                moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
              <a target=3D"_blank" rel=3D"noreferrer nofollow noopener"
                href=3D"https://lists.linuxfoundation.org/mailman/listinf=
o/bitcoin-dev"
                moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext">=
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
            </blockquote>
          </div>
        </blockquote>
        <br>
      </div>
      <br>
      <fieldset class=3D"moz-mime-attachment-header"></fieldset>
      <pre class=3D"moz-quote-pre" wrap=3D"">____________________________=
___________________
bitcoin-dev mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:bitcoin-dev@lists.li=
nuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.linuxfoundation.=
org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailm=
an/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
  </body>
</html>

--------------98CjMHj6Df9j6M4rcHr2hFZj--