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
|
Return-Path: <gsanders87@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 38C2FC002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Oct 2022 13:07:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 082FE8131A
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Oct 2022 13:07:00 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 082FE8131A
Authentication-Results: smtp1.osuosl.org;
dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
header.a=rsa-sha256 header.s=20210112 header.b=CtJLXvLK
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham 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 2St2_yFwI0SC
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Oct 2022 13:06:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org D28B1812FF
Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com
[IPv6:2a00:1450:4864:20::62f])
by smtp1.osuosl.org (Postfix) with ESMTPS id D28B1812FF
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Oct 2022 13:06:56 +0000 (UTC)
Received: by mail-ej1-x62f.google.com with SMTP id ot12so31289734ejb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Oct 2022 06:06:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:from:to:cc:subject:date:message-id:reply-to;
bh=Aqc7io0FTKuL+2uNzlWL+tXVYTiWcrAXQzsl0cPkVCw=;
b=CtJLXvLKi/sg8LP3pEO7Ih2dAqIp2aurt3msNvHdoHrgqw9p8XFu4oOWvuOLCsEewC
mg/SoLN6od2SJ1ovMZ4WJgSTNE5BT5YoPMHxE6r6ZvKIz4Soasp60tg2Pi6AMwNBxbr1
ph8hVheJ0Bf88srUyAbBNCsLMXGeUhONEMePZa7dSbyGlZKgxUujoRRbpW/IGk7ViIdQ
MRkwCMNYKqIXdt0Wa/r/tYZKqhv5F5rFU2QJoce97vScw+8SdB6TR1HJo0ZzAcmC9Wic
9Clwa6oJtGmOm+2cw5kH3xOaV5NfLxtdknTfCFVvRCnDWtXa00khqyxnnIOElRkzqBMp
4iFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
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=Aqc7io0FTKuL+2uNzlWL+tXVYTiWcrAXQzsl0cPkVCw=;
b=rf52HuGl1IVDL6sCIWHhVqm7RerPXAUBZ0bePokxJCN6l4T6Ae8figtf1zL34scNtu
QcCkl1sIu4oBbB29XzivkXNou/OpGLHPQJObs+QGHQBVBMXfaD2VAfgEev8fIocW/tTZ
JFMJo5/k/05iqb2fbpC2oi8cJ+AmIkfaVw4VVMZx1gLt9xNuHtgmEyGceQmpLPdy133E
QjuaJiZ2E1JT55hv5zd/lsGCLIp7mVKQRWN8pCIYReV0+r8cUpzzHYJkUwiSh7BKy4o+
Vl2q3GuaW4rRHI+ojpntJHe3ylZuaiNilShqBs08jO9bNKpEy8iMyjy4f/zdAbFzEA25
M7rA==
X-Gm-Message-State: ACrzQf31Q0K+r3g8kelpwWcoaRZiKr6O2Mjs6XzDcbK/AwG7dvHv9Olm
Tg5XiQf9KrzzxSWKWVvyU9+3nj43lclABh/NdHj20IlV7kA=
X-Google-Smtp-Source: AMsMyM4eN9xugI4/mARAZKrfldOo38WAbf7n5/yNBOFZ99qE5KjykH1yejvP0mfUWXRt1NgrB6KED4VNNr+UII90wOk=
X-Received: by 2002:a17:907:3f8b:b0:783:2008:e562 with SMTP id
hr11-20020a1709073f8b00b007832008e562mr19066413ejc.261.1665493614883; Tue, 11
Oct 2022 06:06:54 -0700 (PDT)
MIME-Version: 1.0
References: <6by5pfnBrFYUmFpOtTRyZ0YIxJaKyaJ1tqW3s26_ZHeGZIJssZY0kLvmYqXtoXRK-mMoMbDY-dmKw_mlCUCDYlzolM25ZvkLpr6pvh8t2LY=@cybriq.systems>
<Z9_T0sYBHcJS5M21tyvXa6vAhC1YamBRXzTCll31M4peuHdbo25v4rnycfTbZOgNgmxA4rzTGLuU4lxT9o6tft90N_7-pfAgiY8_2BAX4w8=@cybriq.systems>
In-Reply-To: <Z9_T0sYBHcJS5M21tyvXa6vAhC1YamBRXzTCll31M4peuHdbo25v4rnycfTbZOgNgmxA4rzTGLuU4lxT9o6tft90N_7-pfAgiY8_2BAX4w8=@cybriq.systems>
From: Greg Sanders <gsanders87@gmail.com>
Date: Tue, 11 Oct 2022 09:06:37 -0400
Message-ID: <CAB3F3Dt7g=_roqWabQxs6RA96foUzbJePV154Dhc-d9WirQ+wg@mail.gmail.com>
To: Loki Verloren <loki@cybriq.systems>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000004a784605eac1f3f8"
Subject: Re: [bitcoin-dev] Minor DoS vulnerability in BIP144 lack of tx
witness data size limit
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, 11 Oct 2022 13:07:00 -0000
--0000000000004a784605eac1f3f8
Content-Type: text/plain; charset="UTF-8"
There are a number of issues with adding arbitrary size restrictions to
consensus(I personally think it's additional complexity for negative gain),
but most of all this may resolve in burned coins.
On Tue, Oct 11, 2022 at 6:22 AM Loki Verloren via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> The recent 998 of 999 multisig segwit transaction highlights a problem
> with BIP144. As the solution applied for btcd shows, effectively a single
> transaction witness can be the same as the maximum block size.
>
> 11000 bytes may not be so unreasonable but now there is a special case
> with a block over 33k worth of witness data.
>
> A concrete limit should be set on the maximum size of a transaction
> witness, and this should be discussed in a more general sense about total
> transaction sizes.
>
> In the absence of a specification, it becomes impossible to properly
> implement and the status quo devolves to the actual implementation in the
> bitcoin core repository code.
>
> I think the weight calculation should escalate exponentially to discourage
> putting transactions like this on the chain. The price was equivalent to
> about $5 to do this.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--0000000000004a784605eac1f3f8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><font face=3D"Arial"><span style=3D"font-size:14px">There =
are a number of issues with adding arbitrary size restrictions to consensus=
(I personally think it's additional complexity for negative gain), but =
most of all this may resolve=C2=A0in burned coins.</span></font></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct=
11, 2022 at 6:22 AM Loki Verloren via bitcoin-dev <<a href=3D"mailto:bi=
tcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org<=
/a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div style=3D"font-family:Arial;font-size:14px"><br></div><div>
=20
<div style=3D"font-family:Arial;font-size:14px"><span>The recen=
t 998 of 999 multisig segwit transaction highlights a problem with BIP144. =
As the solution applied for btcd shows, effectively a single transaction wi=
tness can be the same as the maximum block size.</span><div><br></div><div>=
<span>11000 bytes may not be so unreasonable but now there is a special cas=
e with a block over 33k worth of witness data.</span></div><div><br></div><=
div><span>A concrete limit should be set on the maximum size of a transacti=
on witness, and this should be discussed in a more general sense about tota=
l transaction sizes.</span></div><div><br></div><div><span>In the absence o=
f a specification, it becomes impossible to properly implement and the stat=
us quo devolves to the actual implementation in the bitcoin core repository=
code.</span></div><div><br></div><div>I think the weight calculation shoul=
d escalate exponentially to discourage putting transactions like this on th=
e chain. The price was equivalent to about $5 to do this.</div></div><div s=
tyle=3D"font-family:Arial;font-size:14px">
</div>
<br>
</div>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
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>
--0000000000004a784605eac1f3f8--
|
