From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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 To: Bitcoin Development Mailing List Message-Id: 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: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , 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,

A letter has been published advocating for the fin= al review and
activation of OP_CHECKTEMPLATEVERIFY (BIP-119) and OP_CH= ECKSIGFROMSTACK
(BIP-348).

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 th= at the best next step for bitcoin would be to activate
OP_CHECKTEMPLAT= EVERIFY (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-resist= ant 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 w= as first formalized in BIP-119 over 5 years ago. Despite many
attempts= at refinement or replacement, it has remained the most widely
preferr= ed method for enforcing pregenerated transaction sequences using
conse= nsus. 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 Bloc= kstream=E2=80=99s
Elements for at least 8 years. It represents no sign= ificant
computational burden over bitcoin=E2=80=99s most often used op= code, OP_CHECKSIG.
It can be combined with CTV to implement ln-symmetr= y, a longstanding
improvement to Lightning. It also unlocks a variety = of other use cases.

We respectfully ask Bitcoin Core contributor= s to prioritize the review
and integration of CTV (PR #31989 or simila= r) and CSFS (PR #32247 or
similar) within the next six months. We beli= eve this timeline allows for
rigorous final review and activation plan= ning.

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

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

Signed,

Abdel (Starkware)
An= drew Poelstra (@apoelstra)
Ben Carman (@benthecarman)
Ben Kaufman= (@ben-kaufman)
Brandon Black (@reardencode)
Brian Langel (for Fi= ve Bells)
Buck Perley (@puckberley)
Calle (Cashu)
Calvin Kim= (@kcalvinalvin)
Chun Wang (f2pool)
Christian Decker (@cdecker)Coinjoined Chris (Bitsurance.eu)
Evan Kaloudis (for Zeus)
fia= tjaf (@fiatjaf)
Floppy (@1440000bytes)
Gary Krause (@average-gary= )
Harsha Goli (@arshbot)
Hunter Beast (@cryptoquick)
Jad Mub= aslat (@champbronc2)
James O=E2=80=99Beirne (@jamesob)
Jameson Lo= pp (@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)
S= ean Ryan (Anchorage)
Seth for Privacy (for Cake Wallet)
Simanta G= autam (Alpen Labs)
Steven Roose (@stevenroose)
stutxo (@stutxo)Talip (@otaliptus)
mononaut (@mononautical)
vnprc (@vnprc)

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/a86c2737-db79-4f54-9c1d-51beeb765163n%40googlegroups.com.
------=_Part_325059_76242879.1749469252265-- ------=_Part_325058_105448516.1749469252265--