summaryrefslogtreecommitdiff
path: root/c8/e57e15e10cb47cf7722b90d7e67dccc5a4f1a6
blob: 2f716f3e97866ed8aa54815e15ef0ff36c647237 (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
Return-Path: <pete@petertodd.org>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 7CC4CC0029
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  3 Jun 2023 15:50:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 445E2611A5
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  3 Jun 2023 15:50:37 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 445E2611A5
Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key,
 unprotected) header.d=messagingengine.com header.i=@messagingengine.com
 header.a=rsa-sha256 header.s=fm1 header.b=NIAhlQBy
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001,
 RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id N5XKhQIUTJXv
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  3 Jun 2023 15:50:35 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 629AA611A1
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 629AA611A1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  3 Jun 2023 15:50:35 +0000 (UTC)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47])
 by mailout.nyi.internal (Postfix) with ESMTP id 3B8495C0183;
 Sat,  3 Jun 2023 11:50:34 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
 by compute6.internal (MEProxy); Sat, 03 Jun 2023 11:50:34 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:cc:content-type:content-type:date:date
 :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to
 :message-id:mime-version:references:reply-to:sender:subject
 :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm1; t=1685807434; x=1685893834; bh=O+8a1tu6OigeP
 /GqEsnv0Xf+21IAlmK0ThkizVOTpqQ=; b=NIAhlQByagIMn+PoIsBWyHvCqmQkB
 mwqSqNfy9Iw3YKNcVbjfm0xxUwpO+wtNatVl7TfpIwj8wlFcmfUjnPVpEGj0UL6Y
 8VfA6aF2eUtMBwmuscrx8qViCY4Feyzt95iEwqJXz5Pf51i4F1qp0k6vUUvQh1j2
 s1tYLgSAh1nktSoYPmPtxjlt5anu60qzhQ8qXR7gYircBpUcSEhCu4c/Sw9CUB1I
 ks8YUyde+1otQMbGb8cRvUVftrPlwOhyXc6R6e5NyWbhpZG0aymKQYvGWrVKl+5i
 XT9hOCaVxoPRuOK0tOU2OFZ5mprPaJVWn9RZz7gX2n8SSLoy9SLw47Wgg==
X-ME-Sender: <xms:SWF7ZCiqGiBV5tuDZzr2gAK975gi_8QUD6F66aJ2pKhDlIiaXvihuQ>
 <xme:SWF7ZDB_EHWEyHBOOwzI9Dwo7qBB4XQnDTthedSRX9F9VwnMxCAAIycZcJY7Jy8CM
 X-XNMWuT8SmpyaraZw>
X-ME-Received: <xmr:SWF7ZKGf64HgM4IeeEbPiqgf8-KnVt3FOeIee0DNbicSBmgypbZfS8KIHPuXlOi25MVn1IIrYzr0xCuNThx3X3ORAr4Ox1Pz>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeelhedgleegucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne
 cujfgurhepfffhvfevuffkfhggtggujgesghdtreertddtvdenucfhrhhomheprfgvthgv
 rhcuvfhougguuceophgvthgvsehpvghtvghrthhouggurdhorhhgqeenucggtffrrghtth
 gvrhhnpeelvdellefftddukeduffejgfefjeeuheeileeftdfgteduteeggeevueethfej
 tdenucffohhmrghinhepphgvthgvrhhtohguugdrohhrghenucevlhhushhtvghrufhiii
 gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvgesphgvthgvrhhtohguugdr
 ohhrgh
X-ME-Proxy: <xmx:SWF7ZLQJDQ5ftW5TlG-YQOXKTPOiYBnspGdwdyYCrK-b-ge9Gjvw3A>
 <xmx:SWF7ZPydePh6ecdxSt7yY89FDbOSYIFC8tsYWK15rUY9EnHkSQOe-Q>
 <xmx:SWF7ZJ5IgtZvWqVYpTWxmjAz8SxHN26-AjNy2pZLsO34NFM2wF4ngg>
 <xmx:SmF7ZBvNBksd9nB8uvWz84f2IJwc9_EFwBSVeTENQ94vCkO4_csnvg>
Feedback-ID: i525146e8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat,
 3 Jun 2023 11:50:33 -0400 (EDT)
Received: by localhost (Postfix, from userid 1000)
 id F0FB95F930; Sat,  3 Jun 2023 15:50:27 +0000 (UTC)
Date: Sat, 3 Jun 2023 15:50:27 +0000
From: Peter Todd <pete@petertodd.org>
To: Joost Jager <joost.jager@gmail.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <ZHthQ3VsQgPRvV5m@petertodd.org>
References: <CAJBJmV-L4FusaMNV=_7L39QFDKnPKK_Z1QE6YU-wp2ZLjc=RrQ@mail.gmail.com>
 <29ff546a6007cec1a0f85b91541f8e4d@dtrt.org>
 <CAB3F3Dtad8Fqb4R1phFU33SQPoL66nRz3rSHNbAaDSF=RN1NOA@mail.gmail.com>
 <CAJBJmV8Vt_LLH-AEo-fCCs+S6uSy9UwC6QBakWY5tzn9Utwb8w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="qvLuhofuOWT70oaS"
Content-Disposition: inline
In-Reply-To: <CAJBJmV8Vt_LLH-AEo-fCCs+S6uSy9UwC6QBakWY5tzn9Utwb8w@mail.gmail.com>
Cc: Greg Sanders <gsanders87@gmail.com>
Subject: Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
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: Sat, 03 Jun 2023 15:50:37 -0000


--qvLuhofuOWT70oaS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jun 03, 2023 at 11:14:27AM +0200, Joost Jager via bitcoin-dev wrote:
> Depending on policy to mitigate this annex malleability vector could
> mislead developers into believing their transactions are immune to
> replacement, when in fact they might not be. This potential misalignment
> could result in developers and businesses constructing systems based on
> assumptions that could be compromised in the future, mirroring the
> situation that unfolded with zero-confirmation payments and rbf.
>=20
> It may thus be more prudent to permit the utilization of the annex without
> restrictions, inform developers of its inherent risks, and acknowledge th=
at
> Bitcoin, in its present state, might not be ideally suited for certain
> types of applications?

In the specific case of annex replacement leading to larger transactions, in
almost all cases you only care about the annex malleability causing the
transaction to take longer to get mined, due to it being larger. The fact t=
he
transaction has become larger does not matter if the transaction does in fa=
ct
get mined, eg due to an out-of-band payment by the "attacker".

The only exception is the rare cases where some transaction processing
software/hardware has actual limits on transaction size. Eg you could imagi=
ne a
hardware wallet that simply *can't* process a transaction larger than a cer=
tain
size due to a lack of RAM.

I don't think this is a good rational to make use of the annex standard. Qu=
ite
the contrary: we should be thinking about if and how to fix annex malleabil=
ity
in a future soft fork.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--qvLuhofuOWT70oaS
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmR7YTsACgkQLly11TVR
LzcUhA/8DhdcuVyhsHzl0jEJgT+LC68lQsrlmwc58EK7rW0ZipQ8K9IxZ7+S+SkZ
ILQ1q/hEEzFkUpMMsn/PaCV4C05WbD8b1yQSi5HDMnPTlCdXUrYe7REagGsPHJf0
rRYUrG/5FkJV5xE2gWeb5QNC1CT16AARFNzBvZQLm6lOcKqJ912IxS1xy3erkheO
cZOpBzLL2X9Yyl+QQpdyctckvTmLgLVzrWtlbj1VFsr8IuUahv7Ay2qpqU5Qs26p
gFHNKyzsRw0+KXklDiNChzbEv3xB7WFqkeWq8p2rGhwsdklscg61RIG4X8joDKrw
w4qnxMuSt31qc2SKVRZywlz4Pp4sOAugOgv8gJbZm7Cw7cmpOiooNTGgutvNxqqh
sQiYcJYefp2VL9TvcZdtE5rnIwCSM6b8Hk2pGgXJ0wwpSsGORFx+Gp2YhCR4zQtW
sB6HrK2En7AD7+WIZhEI+CjR360uFHT+vbdISKFCo07rfy3Hlb1qU1kzUy6dfP+8
e0ibEoVLc862OyTrthYQ0djUghS7NVDxL3fHM/SMga/noeueJfvnoTOJtej+QYWm
4RzIqWUc25/G7WwduTiiNDXNm3H+qBeCkwKL9u3og50V6iao3TefXpYsl9TEFpb3
kxF/M9or/xtCSs0v/ve51cXNWOgLXtuRLJr7nyMn36DuTi9WOsg=
=gau+
-----END PGP SIGNATURE-----

--qvLuhofuOWT70oaS--