summaryrefslogtreecommitdiff
path: root/93/1db16bec60fff6d025558138a11a1a511f25df
blob: ea6f3a0c3532678130bf9091587d83a68a49e65b (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
Delivery-date: Mon, 09 Jun 2025 04:54:20 -0700
Received: from mail-yw1-f191.google.com ([209.85.128.191])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBCV5B3G674FRBYEWTPBAMGQEW3CN2CY@googlegroups.com>)
	id 1uOb50-0002sh-WF
	for bitcoindev@gnusha.org; Mon, 09 Jun 2025 04:54:20 -0700
Received: by mail-yw1-f191.google.com with SMTP id 00721157ae682-70e7b4e1522sf58886357b3.1
        for <bitcoindev@gnusha.org>; Mon, 09 Jun 2025 04:54:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1749470053; x=1750074853; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:message-id:to:from:date:sender:from:to:cc:subject:date
         :message-id:reply-to;
        bh=minb3pqzk2z887HLXKY1UjwaaGk48JY/vmUjLkWtSNs=;
        b=XNJmT97AZUfv4W1QhPufyduslb2aZLQOD3kViMjrvt37NPPD7Of+6tejr6pOmVUCXN
         c3iVRALWCHanAivObUXSDJsUPvC2ZybbSAqKVIP4AatZA0kJ2b1dnM5QnnTckV3xUWi7
         uABGroabu+moH0PtBznluvdIumhy3/4G2H0keHsyqBv7/quoS1X+d7Pqpl7T38CF/rYi
         9DCHVim/j/ZU2e5zsPXQIfsAGyTNqf1Ubb0jnwtTWFzGnxl+12sc0lEkVOV2DLTfh+cz
         2m0GwW5wwtV6YdwUyJWOnbh8PvdutFQ8mDLkIiebO1RgPvzNzAs1RWbsWsIHaMrfnBsr
         oDnQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1749470053; x=1750074853; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:message-id:to:from:date:from:to:cc:subject:date:message-id
         :reply-to;
        bh=minb3pqzk2z887HLXKY1UjwaaGk48JY/vmUjLkWtSNs=;
        b=b8seBCnm52fYb6yFJUlT5u9SbggDE+SbISGIUX4f+z0l4ccKFmwbujkVcv5YKYQ1oV
         wPAJx34AgVBFQAU5ngzQwqKb1pu/KexwKEeJas7DH8x5vyZ4ga/zpudSTcDwpI658Fnj
         FJ9z+neXB1l3CW59f1UO1wJ6ZvmKJ5VUEzlWyEo5UWu4agQTRLd0OJImFa5+f6vUE71K
         HKpmXszQRvShdwbIdhqAHSXG1V/YkxQeJUmGn5LNc1tx/TywMYyB4emGGwIcTcrTKTiO
         j4gwZ99X4qhsqEHpNzPN43d6p3BzgRyNw/wRmodXO0jRYZlBZZr+RIYjWUYRdJ4fUa04
         oqEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1749470053; x=1750074853;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:message-id:to:from:date:x-beenthere:x-gm-message-state
         :sender:from:to:cc:subject:date:message-id:reply-to;
        bh=minb3pqzk2z887HLXKY1UjwaaGk48JY/vmUjLkWtSNs=;
        b=gNFxngaf8wJPheTXNlxYqDVmYRTR8VwQ0wWd3CkxbkhrGwNs7qogDY4HdlTWw64EUr
         +kd+YGWfCdB1he5deX4evucoG6sD0jlaQVsEW5ZP4vUqI/Q9aveenAwREcEzvGU6JKKm
         dfQT6Hjnq+l0t9uugipPenIpRlQ+F/0RbzEhN6J4rVrR3pcgUHPm3oJlrpKCDpgbSsk2
         Al35O1jqx21lT6uU4J+awjSWvaOKYw+mC78I/QTWHDst2L7KelhnzPiFxgX0wkcGBd9I
         tkz6jLYGajVW8o7r11bFhaxzK8TC3KN8SpNuRHgqWmQUQuKf1MnOzZ/Q3q1Nc6MtO3lI
         ynTA==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCVVGRG25vfBKU940rBrNTYxy1pa2wMkOtITqN5SJk25aRz+K0Es28woDZjpBe593Ba0NQxzWEcIH01a@gnusha.org
X-Gm-Message-State: AOJu0Yy8rU1gJzaurs3BSYrlsB6B6lSkaTg2KpUpXD/7VY6Wxs+Ek8Hj
	DNvwwo1MKhSVbUNJ7+1QoQ4QQlKNLGfSEnYZEUC9Bsk4poAt4HHpuTlZ
X-Google-Smtp-Source: AGHT+IGLE0Kmwb0hrp2e1ndCenhQrvJOnA9wtgwyjQNxiYqbpNotCGG+SYJ0mNkI15prknHabhklNw==
X-Received: by 2002:a05:6902:2406:b0:e81:2e5a:513 with SMTP id 3f1490d57ef6-e81a22ab417mr15733422276.24.1749470052824;
        Mon, 09 Jun 2025 04:54:12 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZdtsimc46kCQPVPAg2AdHmO/uM5PfvjsQexLVXkzYCKFw==
Received: by 2002:a25:ce94:0:b0:e81:8384:b258 with SMTP id 3f1490d57ef6-e8188912e83ls4064759276.0.-pod-prod-00-us;
 Mon, 09 Jun 2025 04:54:08 -0700 (PDT)
X-Received: by 2002:a05:690c:9c0f:b0:70e:2b3b:1b59 with SMTP id 00721157ae682-710f7ad55f6mr177277877b3.3.1749470048338;
        Mon, 09 Jun 2025 04:54:08 -0700 (PDT)
Received: by 2002:a05:690c:fc7:b0:710:fccf:6901 with SMTP id 00721157ae682-710fccf6a41ms7b3;
        Mon, 9 Jun 2025 04:40:53 -0700 (PDT)
X-Received: by 2002:a05:690c:450d:b0:70e:25b2:8f42 with SMTP id 00721157ae682-7110884b089mr103648837b3.18.1749469252592;
        Mon, 09 Jun 2025 04:40:52 -0700 (PDT)
Date: Mon, 9 Jun 2025 04:40:52 -0700 (PDT)
From: James O'Beirne <james.obeirne@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <a86c2737-db79-4f54-9c1d-51beeb765163n@googlegroups.com>
Subject: [bitcoindev] CTV + CSFS: a letter
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_325058_105448516.1749469252265"
X-Original-Sender: james.obeirne@gmail.com
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.5 (/)

------=_Part_325058_105448516.1749469252265
Content-Type: multipart/alternative; 
	boundary="----=_Part_325059_76242879.1749469252265"

------=_Part_325059_76242879.1749469252265
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Good morning,

A letter has been published advocating for the final review and
activation of OP_CHECKTEMPLATEVERIFY (BIP-119) and OP_CHECKSIGFROMSTACK
(BIP-348).=20

The full text of the letter can be found at https://ctv-csfs.com. It is
reproduced below.

---

To the technical bitcoin community,

We believe that the best next step for bitcoin would be to activate
OP_CHECKTEMPLATEVERIFY (CTV, BIP-119) and OP_CHECKSIGFROMSTACK (CSFS,
BIP-348). These opcodes enable functionality for a broad set of uses
that will allow bitcoin to preserve and expand its role as a scarce,
censorship-resistant store of value.

While there are a few promising proposals to improve bitcoin at the
consensus layer which may someday be deployed, we believe that CTV and
CSFS are uniquely well reviewed, simple, and have been proven to be both
safe and widely demanded.

CTV was first formalized in BIP-119 over 5 years ago. Despite many
attempts at refinement or replacement, it has remained the most widely
preferred method for enforcing pregenerated transaction sequences using
consensus. It unlocks valuable functionality for scaling solutions,
vaults, congestion control, non-custodial mining, discreet log
contracts, and more.

CSFS is a primitive opcode that has been deployed to Blockstream=E2=80=99s
Elements for at least 8 years. It represents no significant
computational burden over bitcoin=E2=80=99s most often used opcode, OP_CHEC=
KSIG.
It can be combined with CTV to implement ln-symmetry, a longstanding
improvement to Lightning. It also unlocks a variety of other use cases.

We respectfully ask Bitcoin Core contributors to prioritize the review
and integration of CTV (PR #31989 or similar) and CSFS (PR #32247 or
similar) within the next six months. We believe this timeline allows for
rigorous final review and activation planning.

This request isn't meant to suggest that these contributors dictate the
consensus process, but rather it is an acknowledgement that before these
opcodes can be activated, they must be implemented in the most widely
used bitcoin client.

As application and protocol developers, we are convinced of the
significant benefits that these changes would bring to end users of
bitcoin =E2=80=93 even if only considering their use for layer 1 security a=
nd
layer 2 scaling solutions. We are optimistic that given the limited size
and scope of these changes in both concept and implementation, they
represent a realistic next step in the continuing and important work of
preserving bitcoin's unique promise.

Signed,=20

Abdel (Starkware)
Andrew Poelstra (@apoelstra)
Ben Carman (@benthecarman)
Ben Kaufman (@ben-kaufman)
Brandon Black (@reardencode)
Brian Langel (for Five Bells)
Buck Perley (@puckberley)
Calle (Cashu)
Calvin Kim (@kcalvinalvin)
Chun Wang (f2pool)
Christian Decker (@cdecker)
Coinjoined Chris (Bitsurance.eu)
Evan Kaloudis (for Zeus)
fiatjaf (@fiatjaf)
Floppy (@1440000bytes)
Gary Krause (@average-gary)
Harsha Goli (@arshbot)
Hunter Beast (@cryptoquick)
Jad Mubaslat (@champbronc2)
James O=E2=80=99Beirne (@jamesob)
Jameson Lopp (@jlopp)
Johan Halseth (@halseth)
Luke Childs (@lukechilds)
Matt Black (for Atomic Finance)
Michael Tidwell (@miketwenty1)
Nick Hansen (for Luxor Mining)
Nitesh (@nitesh_btc)
nvk (@nvk)
Owen Kemeys (for Foundation)
Paul Sztorc (@psztorc)
Portland.HODL (for MARA Pool)
Rijndael (@rot13maxi)
Rob Hamilton (@rob1ham)
Robin Linus (@RobinLinus)
Sanket Kanjalkar (@sanket1729)
Sean Ryan (Anchorage)
Seth for Privacy (for Cake Wallet)
Simanta Gautam (Alpen Labs)
Steven Roose (@stevenroose)
stutxo (@stutxo)
Talip (@otaliptus)
mononaut (@mononautical)
vnprc (@vnprc)

--=20
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 e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
a86c2737-db79-4f54-9c1d-51beeb765163n%40googlegroups.com.

------=_Part_325059_76242879.1749469252265
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Good morning,<br /><br />A letter has been published advocating for the fin=
al review and<br />activation of OP_CHECKTEMPLATEVERIFY (BIP-119) and OP_CH=
ECKSIGFROMSTACK<br />(BIP-348). <br /><br />The full text of the letter can=
 be found at https://ctv-csfs.com. It is<br />reproduced below.<br /><br />=
---<br /><br />To the technical bitcoin community,<br /><br />We believe th=
at the best next step for bitcoin would be to activate<br />OP_CHECKTEMPLAT=
EVERIFY (CTV, BIP-119) and OP_CHECKSIGFROMSTACK (CSFS,<br />BIP-348). These=
 opcodes enable functionality for a broad set of uses<br />that will allow =
bitcoin to preserve and expand its role as a scarce,<br />censorship-resist=
ant store of value.<br /><br />While there are a few promising proposals to=
 improve bitcoin at the<br />consensus layer which may someday be deployed,=
 we believe that CTV and<br />CSFS are uniquely well reviewed, simple, and =
have been proven to be both<br />safe and widely demanded.<br /><br />CTV w=
as first formalized in BIP-119 over 5 years ago. Despite many<br />attempts=
 at refinement or replacement, it has remained the most widely<br />preferr=
ed method for enforcing pregenerated transaction sequences using<br />conse=
nsus. It unlocks valuable functionality for scaling solutions,<br />vaults,=
 congestion control, non-custodial mining, discreet log<br />contracts, and=
 more.<br /><br />CSFS is a primitive opcode that has been deployed to Bloc=
kstream=E2=80=99s<br />Elements for at least 8 years. It represents no sign=
ificant<br />computational burden over bitcoin=E2=80=99s most often used op=
code, OP_CHECKSIG.<br />It can be combined with CTV to implement ln-symmetr=
y, a longstanding<br />improvement to Lightning. It also unlocks a variety =
of other use cases.<br /><br />We respectfully ask Bitcoin Core contributor=
s to prioritize the review<br />and integration of CTV (PR #31989 or simila=
r) and CSFS (PR #32247 or<br />similar) within the next six months. We beli=
eve this timeline allows for<br />rigorous final review and activation plan=
ning.<br /><br />This request isn't meant to suggest that these contributor=
s dictate the<br />consensus process, but rather it is an acknowledgement t=
hat before these<br />opcodes can be activated, they must be implemented in=
 the most widely<br />used bitcoin client.<br /><br />As application and pr=
otocol developers, we are convinced of the<br />significant benefits that t=
hese changes would bring to end users of<br />bitcoin =E2=80=93 even if onl=
y considering their use for layer 1 security and<br />layer 2 scaling solut=
ions. We are optimistic that given the limited size<br />and scope of these=
 changes in both concept and implementation, they<br />represent a realisti=
c next step in the continuing and important work of<br />preserving bitcoin=
's unique promise.<br /><br />Signed, <br /><br />Abdel (Starkware)<br />An=
drew Poelstra (@apoelstra)<br />Ben Carman (@benthecarman)<br />Ben Kaufman=
 (@ben-kaufman)<br />Brandon Black (@reardencode)<br />Brian Langel (for Fi=
ve Bells)<br />Buck Perley (@puckberley)<br />Calle (Cashu)<br />Calvin Kim=
 (@kcalvinalvin)<br />Chun Wang (f2pool)<br />Christian Decker (@cdecker)<b=
r />Coinjoined Chris (Bitsurance.eu)<br />Evan Kaloudis (for Zeus)<br />fia=
tjaf (@fiatjaf)<br />Floppy (@1440000bytes)<br />Gary Krause (@average-gary=
)<br />Harsha Goli (@arshbot)<br />Hunter Beast (@cryptoquick)<br />Jad Mub=
aslat (@champbronc2)<br />James O=E2=80=99Beirne (@jamesob)<br />Jameson Lo=
pp (@jlopp)<br />Johan Halseth (@halseth)<br />Luke Childs (@lukechilds)<br=
 />Matt Black (for Atomic Finance)<br />Michael Tidwell (@miketwenty1)<br /=
>Nick Hansen (for Luxor Mining)<br />Nitesh (@nitesh_btc)<br />nvk (@nvk)<b=
r />Owen Kemeys (for Foundation)<br />Paul Sztorc (@psztorc)<br />Portland.=
HODL (for MARA Pool)<br />Rijndael (@rot13maxi)<br />Rob Hamilton (@rob1ham=
)<br />Robin Linus (@RobinLinus)<br />Sanket Kanjalkar (@sanket1729)<br />S=
ean Ryan (Anchorage)<br />Seth for Privacy (for Cake Wallet)<br />Simanta G=
autam (Alpen Labs)<br />Steven Roose (@stevenroose)<br />stutxo (@stutxo)<b=
r />Talip (@otaliptus)<br />mononaut (@mononautical)<br />vnprc (@vnprc)<br=
 /><br />

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/a86c2737-db79-4f54-9c1d-51beeb765163n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/a86c2737-db79-4f54-9c1d-51beeb765163n%40googlegroups.com</a>.<br />

------=_Part_325059_76242879.1749469252265--

------=_Part_325058_105448516.1749469252265--