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
|
Delivery-date: Wed, 30 Jul 2025 09:06:25 -0700
Received: from mail-oo1-f64.google.com ([209.85.161.64])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBAABB54FVHCAMGQEE5KOBJI@googlegroups.com>)
id 1uh9Jw-0000IN-Jm
for bitcoindev@gnusha.org; Wed, 30 Jul 2025 09:06:24 -0700
Received: by mail-oo1-f64.google.com with SMTP id 006d021491bc7-61904838bf9sf4734105eaf.2
for <bitcoindev@gnusha.org>; Wed, 30 Jul 2025 09:06:24 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1753891578; cv=pass;
d=google.com; s=arc-20240605;
b=Et/7vg3L2llUeFSA/u6qcvYAVyqOd9DxHvfmO4f2kRQuwMHVD2na+l4eGGOIzNm7Bj
GRUIV/A+N3wPylGoB/SjJzHmdgo20VweErP9VrwTIMRPcwS4Q1hu1tQOyniuQxYLbFq4
ACp59QJiwYTvIzOpOVD8HhIODQSS8XRwdIb/aIW+oHuRAvbQxv7zXU2Z04TjeEzBVu4p
qlKoyaa613h7PwrNdz/5ynzDPpjqA0h0Rxr1+bXAnKosc5nNhs2/Jr/sC1rRc+ahXW1j
bYHNgxIvzEu0FCT0c5OgXXlmLIs1zEhQbK2JXxGzHFffRoH4f8YnDPMU3D4Bf/hUsF64
RbQA==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:to:references:message-id:cc:date
:in-reply-to:from:subject:mime-version:feedback-id:sender
:dkim-signature;
bh=Q+Y+SMQXxZkARokr1bmyED3KLolh7Le5QveDNt0KRD0=;
fh=ZXNJ8ADfiwuMqgkTAiyUi84QpSeEZ6XsbFRx8cB2JZE=;
b=gU7NyhAckfyh6jNvZ1j+xErfzoBKM1UT+n0+asssa1Q1tkrhKvGRQqo053CwEyriZp
1OidNeeczwYEbVoe67nFGAfIN8msR5AdDJGEprAMS2NAEpc8Qi3Xv8jAfPpkSNQb+uK6
YyJFD+uxCp7atBHKlj4UHT7IYGMyw8PSGtdAXcn8UWG/pGei+4u2Cmy3TDsm8WRaNkdD
Trbjr1nnQdBDJi9bJLHKlJghF1Lgzl0QM/UNlfkU5bZtfVLSo6VMm5f31ujEo3jrsfET
7mJMd0xkQ/7mXFo2VhaSZ43Csqo02OFzB4vQGjNmcjnFk8W2zjLlO4Ido1oixSvJ6f4m
DmgA==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
dkim=pass header.i=@sprovoost.nl header.s=fm1 header.b=RYRZ7u60;
dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=E1j2sYJa;
spf=pass (google.com: domain of sjors@sprovoost.nl designates 202.12.124.154 as permitted sender) smtp.mailfrom=sjors@sprovoost.nl;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sprovoost.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1753891578; x=1754496378; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:to:references:message-id:cc:date:in-reply-to:from
:subject:mime-version:feedback-id:sender:from:to:cc:subject:date
:message-id:reply-to;
bh=Q+Y+SMQXxZkARokr1bmyED3KLolh7Le5QveDNt0KRD0=;
b=auLk/Ci84GRiYoyyoODbuotaUOHK8ynh9H5hhP+rqdvdplZzhu3mG71qEpj280DShB
zqveSL967zJnEXK2uqeBw2/dcJ17IJ7Nh9x9euvFSoiDyDj48vb4E1Hyzn8JAS7sOIUC
SipUnVR0WoCFQNiEnAXyMpqPUm9luD/T1+G7efQ14AW1ZnfB5EYSW2QKYL0/ANvuTbBl
vBzdM8OhfuYKo4XnA3Z5sKIosglP+sgbSwj+eBHZfk16KClbfsjW+pOABUfEMm1Y08GM
wXKZhY8driBymy9kQ1Ha1ub71hsoJyareFLLoXogdU5jJnYejvlwSzM0owwvCVVtBRoM
izew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1753891578; x=1754496378;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:to:references:message-id:cc:date:in-reply-to:from
:subject:mime-version:feedback-id:x-beenthere:x-gm-message-state
:sender:from:to:cc:subject:date:message-id:reply-to;
bh=Q+Y+SMQXxZkARokr1bmyED3KLolh7Le5QveDNt0KRD0=;
b=BTDKj4jy4z7KDNuC0gEGuCQWIuOWaqd8ejeSA6NeFtKv6UqGwm77WD/KmXcNK6LM3a
VmVGfQxSSN0oVAD++We4k2LMEo7ccuujBsi8boiHxDVabcdJy7ENZeGeAHKAwwrDv0jL
QEpdq72n3xDaeQgePAPYUyOvDujjP1/sd+R4rVt1UCIIUwAf6Wlb+clT92C/gMB26ynL
Mr1TGA0lSmS7gf9idLQNXK0BeqPWO7mvL8CgAaavgJT9vrkXY0EGCwY8xsuiosW5CL2I
sIIh/YcexClHnEzVmmvmDA5uXed7Ik0VZB6J+6L6mjOex70c3u21OAThXWJof/IfqW8s
ACXQ==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCWNeyj5eH8MGEm2CVMCK7sNztKS0ko8EgEzak9auQwKl8XofBew0CkyO+f69xpWGFEmhJUpbZweqQt5@gnusha.org
X-Gm-Message-State: AOJu0YxyPOkToAvY3val6WmHbX/skizjrb3RZvxWbvVKSP6hjtLPhjE4
BOiqOe2s29jgqvQPS+Q/BjKJt2eFWDacE7tgrkOSfgmfnPildxgq58rF
X-Google-Smtp-Source: AGHT+IGZYeH8odDAoxtxryquslP18C2mypRBe5SnISdeVnZd6mE8h2H3dOqk3ZOwxPVFNxZEFKdmQw==
X-Received: by 2002:a05:6820:993:b0:619:12c7:978 with SMTP id 006d021491bc7-6195d454815mr2400055eaf.6.1753891578168;
Wed, 30 Jul 2025 09:06:18 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZcMG+Cwc8DMcN94h/EYCvBUZkDPbVo5osmhXp4PTUXcoA==
Received: by 2002:a05:6820:2f09:b0:611:96d6:4597 with SMTP id
006d021491bc7-618fa2dff36ls1301800eaf.2.-pod-prod-07-us; Wed, 30 Jul 2025
09:06:14 -0700 (PDT)
X-Received: by 2002:a05:6808:13d6:b0:3fe:aecb:5c49 with SMTP id 5614622812f47-4319b630a0amr2576391b6e.21.1753891574782;
Wed, 30 Jul 2025 09:06:14 -0700 (PDT)
Received: by 2002:a05:6808:dc4:b0:40d:498:c1f6 with SMTP id 5614622812f47-4319dc6c3a2msb6e;
Wed, 30 Jul 2025 08:40:40 -0700 (PDT)
X-Received: by 2002:a05:6870:72ce:b0:2ff:92c6:51f6 with SMTP id 586e51a60fabf-30785a2b0e7mr2336778fac.15.1753890039756;
Wed, 30 Jul 2025 08:40:39 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1753890039; cv=none;
d=google.com; s=arc-20240605;
b=ApBh2COv28hlw0MoZU6f+t5KcNgZW5/5ZL2zBzu/rfg47yTXcN/0txNm2poXYdp9Ge
MbjlO+0HlgGa36ZjBRtgsLigeNXUKJoxSMMzKbMzu5SBUfHMbSaW3N2H1iehC5YIKF4J
89Th1o/Zgn4DsCJTYzVHNCWrsRs2E1mbeGfDyyEVsJYq3Fvb/GpNO+dasoBadruFE7Td
6uMODfA45MAwxKp9PcX6wr+2WR1xSE7unAl7EaiKaP4zPRUO1cxa7Y+QFVgEHKj9O84b
QHlSEsR6lHS4af3r+zJk7i1v8FifqLsjvQcZKOZnks6Wa1Mm/hR5vOKHuWeMliyHeqsw
84Hw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=to:references:message-id:content-transfer-encoding:cc:date
:in-reply-to:from:subject:mime-version:feedback-id:dkim-signature
:dkim-signature;
bh=tKafjycAtKpf47CpIS920eIXSYhgGh882KEGOCpcp50=;
fh=AqIHahSuKP+HnsWhbmsueMY/Hx8M/EEIUs+Ij8y4X7k=;
b=Jga2D6XmlUUnulh6EYMF9hzL9BX6OSQBF94+r3cZWGfA52r+LsfOIsMw0CVl2xN49o
+Vvbi2Bd+zUFyKXZqiD3qK56KkGSUPKYHLfW0SCAkvnkkoq2cLQwO9RJTMc4hkz2vAlg
+sOdm4T3/gGwJPXL0JsBVCnDCNnK5i3EEb+kxL1c/VwSsgp2HT9NVsKl451Saphju3Yz
wqC/s+TnZ4/mxYUVUh9xJbcQkUtzNaEJJJRRN84qLFpDxKUYhi+Eldsl0fbeT2nZdLwO
sNSE4D6k385hoZ6MyhEQlo+Tms6OuXvcikMnGxLjcm7ojPLXJ4CBzFAcAUMzGqlGPcti
Z+HA==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
dkim=pass header.i=@sprovoost.nl header.s=fm1 header.b=RYRZ7u60;
dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=E1j2sYJa;
spf=pass (google.com: domain of sjors@sprovoost.nl designates 202.12.124.154 as permitted sender) smtp.mailfrom=sjors@sprovoost.nl;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sprovoost.nl
Received: from fhigh-b3-smtp.messagingengine.com (fhigh-b3-smtp.messagingengine.com. [202.12.124.154])
by gmr-mx.google.com with ESMTPS id 586e51a60fabf-30712fff7e5si567285fac.1.2025.07.30.08.40.39
for <bitcoindev@googlegroups.com>
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Wed, 30 Jul 2025 08:40:39 -0700 (PDT)
Received-SPF: pass (google.com: domain of sjors@sprovoost.nl designates 202.12.124.154 as permitted sender) client-ip=202.12.124.154;
Received: from phl-compute-01.internal (phl-compute-01.phl.internal [10.202.2.41])
by mailfhigh.stl.internal (Postfix) with ESMTP id 720607A220A;
Wed, 30 Jul 2025 11:40:38 -0400 (EDT)
Received: from phl-mailfrontend-02 ([10.202.2.163])
by phl-compute-01.internal (MEProxy); Wed, 30 Jul 2025 11:40:38 -0400
X-ME-Sender: <xms:9TyKaGvXM_ybZoKZANfwDnCxYZbFomSSLdSawRq5UeTeE5isZwEM7Q>
<xme:9TyKaGXkE8S10m1y2UrAaQdIqLRmG8iHpgcMCFmH6hmE9JAX0Hc9moHhVKYbDiluu
QhgyD-NWQex7ipoIw>
X-ME-Received: <xmr:9TyKaJm99eG0GqIXDV-Xd-wKYsuEp_md_mbtY_j_Uy2U9xE8mCmi2ln6qS0_fsrDlKct>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdelkeefvdcutefuodetggdotefrod
ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr
ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug
hrpegtggfuhfgjffevgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepufhjohhrshcu
rfhrohhvohhoshhtuceoshhjohhrshesshhprhhovhhoohhsthdrnhhlqeenucggtffrrg
htthgvrhhnpeevkeelgfffgffgffelfefhgfdtvdduffdtudetieejvdejveekkeegffej
teefjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe
hsjhhorhhssehsphhrohhvohhoshhtrdhnlhdpnhgspghrtghpthhtohepgedpmhhouggv
pehsmhhtphhouhhtpdhrtghpthhtohepuggrrhhoshhiohhrsehprhhothhonhhmrghilh
drtghomhdprhgtphhtthhopehjrghmvghsrdhosggvihhrnhgvsehgmhgrihhlrdgtohhm
pdhrtghpthhtohepghhsrghnuggvrhhskeejsehgmhgrihhlrdgtohhmpdhrtghpthhtoh
epsghithgtohhinhguvghvsehgohhoghhlvghgrhhouhhpshdrtghomh
X-ME-Proxy: <xmx:9TyKaPY97-IW5ev_b2mLPPtWgTf8M6kUQZ4yU3H5lsoNpNQU7wHcDw>
<xmx:9TyKaMNzcN2uZArk_g-xeVtOtckqX5xrLcDb3XGV_QYB2GtSjmIWFQ>
<xmx:9TyKaMax589cC1im8qJg-pi6-tthcofQ7EtBhn3dm6EfkwRTsDQQwg>
<xmx:9TyKaC3jfJQ01Uk9xCaMdTdeROxswg4yfQ40S6mqiknLRui-GID2cw>
<xmx:9jyKaCBAScBfSy1JUB3otARJcEes3OfQj77rmPsrDiW2HFV8bI97J8Ky>
Feedback-ID: ie5e042df:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed,
30 Jul 2025 11:40:37 -0400 (EDT)
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: [bitcoindev] A Taproot-native (re-)bindable transaction bundle proposal
From: Sjors Provoost <sjors@sprovoost.nl>
In-Reply-To: <_POzkO7sHDURx6skGAWsrxN_UUtN_6Ak6donzVhmzYzAV6Ej22jBnE2baxM_WtqxW2RNvDjze72kOVgowNhqGSJ1dg5m_HTO3FuG6QM5daw=@protonmail.com>
Date: Wed, 30 Jul 2025 17:40:25 +0200
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <4E54B8EA-9BE8-4660-AA29-72E14C3AADF5@sprovoost.nl>
References: <26b96fb1-d916-474a-bd23-920becc3412cn@googlegroups.com>
<CAPfvXf+E0YDzqY_jsGVoc4KKh_Kgsp-p20wNAD05tv_rMNG2sA@mail.gmail.com>
<_POzkO7sHDURx6skGAWsrxN_UUtN_6Ak6donzVhmzYzAV6Ej22jBnE2baxM_WtqxW2RNvDjze72kOVgowNhqGSJ1dg5m_HTO3FuG6QM5daw=@protonmail.com>
To: Antoine Poinsot <darosior@protonmail.com>,
James O'Beirne <james.obeirne@gmail.com>,
Greg Sanders <gsanders87@gmail.com>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
X-Original-Sender: sjors@sprovoost.nl
X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass
header.i=@sprovoost.nl header.s=fm1 header.b=RYRZ7u60; dkim=pass
header.i=@messagingengine.com header.s=fm3 header.b=E1j2sYJa; spf=pass
(google.com: domain of sjors@sprovoost.nl designates 202.12.124.154 as
permitted sender) smtp.mailfrom=sjors@sprovoost.nl; dmarc=pass (p=NONE
sp=NONE dis=NONE) header.from=sprovoost.nl
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.8 (/)
Regarding the (lack of) support of v0 SegWit, James O'Beirne wrote:
> To date I haven't heard any concrete downside of including witness v0
> support for an opcode like this other than "it's marginally more to
> think about during review."
I wouldn't discount that argument though. It's very nice to not have to think about any of the problems that v1 (taproot) already fixed. We know that review has been a major bottleneck for these proposals.
That said, it may be useful to have a "patch" for both the BIP text and the implementation that does support v0. I'm sure it's a lot less scary than pre-SegWit support.
> One concrete impediment to Taproot adoption among custodians is the lack
> of native HSM support for the Schnorr signature scheme. It's reasonable
> to believe that some already-deployed HSM contexts may never get to
> Taprootability.
I find it worrying that companies claiming to build military grade ultra secure hardware, that are used protect hundred of billions of dollars, have refused to implement Schnorr signatures for 5+ years now.
It also means they can't support MuSig2 and instead have to use ECDSA signature aggregation. They also can't support script path spending, which isn't great for privacy.
I guess we'll have to wait until enough other crypto chains migrate to Schnorr so there's enough trade volume to justify paying an engineer to spend two weeks fixing this firmware.
That said, I don't use such services (for more than a few minutes) and I don't think we should "force" people to upgrade by stubbornly not supporting v0.
- Sjors
> Op 11 jul 2025, om 20:37 heeft 'Antoine Poinsot' via Bitcoin Development Mailing List <bitcoindev@googlegroups.com> het volgende geschreven:
[...]
> Your second main criticism concerns the lack of Segwit v0 support. You start by cherry-picking some
> data about Taproot's usage, so i'll ask you to please keep the discussion honest here. You state
> that between 0.1% and 0.75% of all bitcoins in existence are held in P2TR outputs, and use this
> figure to conclude the "overwhelming majority of **value transfer** in bitcoin is still happening in
> a pre-Taproot script context". This non-sequitur reads as though you'd already settled on the
> conclusion and were reaching for data that might appear to support it. In 2024 and 2025 between 20%
> and 40% of all onchain transfers used Taproot[^0] (vs between 1% and 3% for P2WSH). Even
> considering the value of these transfers gives a pretty clear trajectory: since the beginning of
> 2024 the percentage of BTC getting locked into P2TR outputs quadrupled from 2.2% to 8.5%[^1] (the
> percentage for P2WSH was steady from 16.4% to 16.8%).
>
> I strongly believe our default position should be to only enable new features in the latest
> iteration of the scripting system. While Segwit v0 fixed the most important quirks of legacy Script,
> Taproot/Tapscript finishes this work by removing the remaining instances of quadratic hashing,
> enforcing by consensus more malleability-related standardness rules, being compatible with batched
> validation today and a possible future CISA, and finally presenting the slight but still good to
> have privacy improvement that all outputs look the same before being spent (and sometimes even after
> being spent although it's harder to achieve). We should not provide new features for an outdated
> scripting context unless we have a strong reason to.
>
> I don't think you provide a strong reason not to stick to Tapscript. You claim that many industrial
> players would not be able to use OP_TEMPLATEHASH but you don't back it up with anything
> demonstrating those companies 1) desire to use OP_TEMPLATEHASH and jointly 2) are somehow unable to
> upgrade from P2WSH to Taproot.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/4E54B8EA-9BE8-4660-AA29-72E14C3AADF5%40sprovoost.nl.
|
