path: root/f8/f667bbfa2c713ace990f936894d07b95d8874e

Return-Path: <ryan@breen.xyz>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 93426C0037
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  2 Jan 2024 16:30:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 50BD841528
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  2 Jan 2024 16:30:17 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 50BD841528
Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key,
 unprotected) header.d=breen.xyz header.i=@breen.xyz header.a=rsa-sha256
 header.s=sig1 header.b=WYvcK/7u
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.298
X-Spam-Level: 
X-Spam-Status: No, score=-0.298 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, FROM_SUSPICIOUS_NTLD=0.499,
 HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, PDS_OTHER_BAD_TLD=1.999,
 RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001,
 RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=no autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id tTSx5e7Cc3OJ
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  2 Jan 2024 16:30:16 +0000 (UTC)
X-Greylist: delayed 357 seconds by postgrey-1.37 at util1.osuosl.org;
 Tue, 02 Jan 2024 16:30:16 UTC
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 48FD941488
Received: from st43p00im-ztfb10063301.me.com (st43p00im-ztfb10063301.me.com
 [17.58.63.179])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 48FD941488
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  2 Jan 2024 16:30:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=breen.xyz; s=sig1;
 t=1704212658; bh=mp4NFIB3A4qPx5MyQ0xyv+aTEJcg0TCcAKuElCs2qG4=;
 h=Content-Type:From:Mime-Version:Subject:Date:Message-Id:To;
 b=WYvcK/7uGp4I7TzmEmChRWaUtBchTbsBAg8ei4OEvi4+/IJoHnY8cCbrfhZ4uzXCc
 /EnEqzy5xMeWZ2Fp0zoZc33VDL+FFalQH4paI+sgBJjJAq5NO/vh44MKYqhi0QTT//
 AhgjpaA/Oovl3Zq3lfNP9KTl4mDRVumlTXkxlgPNxVBHjbsbngcjlQUErxYQYkfNE/
 zTgp1HWyRLglKKqokngMK4G3ETJPAhIEBz10U3GLKJ/adVGwN9xFnPnwCwwRKLaVag
 ZwuumnTZj5T0IaJixVjn9CcjHUydxvDwfSt6y8rpSeiuz8LLfgnwMfN9XRaorJ8EhY
 B2hgnAuK0rI1w==
Received: from smtpclient.apple (st43p00im-dlb-asmtp-mailmevip.me.com
 [17.42.251.41])
 by st43p00im-ztfb10063301.me.com (Postfix) with ESMTPSA id C3443700A16;
 Tue,  2 Jan 2024 16:24:17 +0000 (UTC)
Content-Type: multipart/alternative;
 boundary=Apple-Mail-4AB29EF3-859C-4240-8AAE-8C045A8DFA40
Content-Transfer-Encoding: 7bit
From: Ryan Breen <ryan@breen.xyz>
Mime-Version: 1.0 (1.0)
Date: Tue, 2 Jan 2024 11:24:06 -0500
Message-Id: <5E185ABF-9F36-427D-B30D-D1E26D198469@breen.xyz>
References: <Zzpp9sp69_QmkUre4YUawBxOLECIfHHUf_OoD8UXXZ8Xwtmr5R62_rlGV2iwLivkST-vWusc0X9horY9qHEHKP2g4GR2ppCAuIE57VANUP0=@protonmail.com>
In-Reply-To: <Zzpp9sp69_QmkUre4YUawBxOLECIfHHUf_OoD8UXXZ8Xwtmr5R62_rlGV2iwLivkST-vWusc0X9horY9qHEHKP2g4GR2ppCAuIE57VANUP0=@protonmail.com>
To: Michael Folkson <michaelfolkson@protonmail.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPhone Mail (21C66)
X-Proofpoint-ORIG-GUID: AeSeDAmR4bg3pR2NGuwJfQup7JDeMo4i
X-Proofpoint-GUID: AeSeDAmR4bg3pR2NGuwJfQup7JDeMo4i
X-Proofpoint-Virus-Version: vendor=baseguard
 engine=ICAP:2.0.272,Aquarius:18.0.997,Hydra:6.0.619,FMLib:17.11.176.26
 definitions=2024-01-02_05,2024-01-02_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0
 spamscore=0 adultscore=0
 suspectscore=0 malwarescore=0 bulkscore=0 clxscore=1030 mlxlogscore=927
 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.19.0-2308100000 definitions=main-2401020124
X-Mailman-Approved-At: Wed, 03 Jan 2024 16:20:16 +0000
Subject: Re: [bitcoin-dev] Swift Activation - CTV
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, 02 Jan 2024 16:30:17 -0000


--Apple-Mail-4AB29EF3-859C-4240-8AAE-8C045A8DFA40
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



> On Jan 2, 2024, at 10:50=E2=80=AFAM, Michael Folkson via bitcoin-dev <bitc=
oin-dev@lists.linuxfoundation.org> wrote:
>=20
> Your knowledge is incorrect. As far as I know in the getting on for 2 year=
s since the first CTV activation talk/attempt literally no one has built out=
 a CTV use case and demonstrated it on signet with the possible exception of=
 James O'Beirne's OP_VAULT which requires other new opcodes in addition to C=
TV. I wish this wasn't the case. It is pitiful that we have these individual=
s (such as yourself) that are so convinced CTV should be activated but refus=
e to address any concerns raised by others and refuse to work on any of the s=
peculated use cases, instead choosing to just beat the activation drum over a=
nd over again.

James O=E2=80=99Beirne built a CTV-only vault prototype[1], actually. Jeremy=
 Rubin also built vaults and many other prototypes with his Sapio smart cont=
racting language.[2]

So this assertion that CTV has had no use cases or prototypes built out for i=
t is just not true.

[1]: https://github.com/jamesob/simple-ctv-vault
[2]: https://github.com/sapio-lang/sapio=

--Apple-Mail-4AB29EF3-859C-4240-8AAE-8C045A8DFA40
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr"><br=
></div><div dir=3D"ltr"><br><blockquote type=3D"cite">On Jan 2, 2024, at 10:=
50=E2=80=AFAM, Michael Folkson via bitcoin-dev &lt;bitcoin-dev@lists.linuxfo=
undation.org&gt; wrote:<br></blockquote></div><blockquote type=3D"cite"><div=
 dir=3D"ltr"><div style=3D"font-size: 14px;"><div dir=3D"auto" style=3D"font=
-family: system-ui, sans-serif; line-height: 1.5;"><br></div><div dir=3D"aut=
o" style=3D"font-family: system-ui, sans-serif; line-height: 1.5;">Your know=
ledge is incorrect. As far as I know in the getting on for 2 years since the=
 first CTV activation talk/attempt literally no one has built out a CTV use c=
ase and demonstrated it on signet with the possible exception of James O'Bei=
rne's OP_VAULT which requires other new opcodes in addition to CTV. I wish t=
his wasn't the case. It is pitiful that we have these individuals (such as y=
ourself) that are so convinced CTV should be activated but refuse to address=
 any concerns raised by others and refuse to work on any of the speculated u=
se cases, instead choosing to just beat the activation drum over and over ag=
ain.</div></div></div></blockquote><br><div>James O=E2=80=99Beirne built a C=
TV-only vault prototype[1], actually. Jeremy Rubin also built vaults and man=
y other prototypes with his Sapio smart contracting language.[2]</div><div><=
br></div><div>So this assertion that CTV has had no use cases or prototypes b=
uilt out for it is just not true.</div><div><br></div><div>[1]:&nbsp;<a href=
=3D"https://github.com/jamesob/simple-ctv-vault">https://github.com/jamesob/=
simple-ctv-vault</a></div><div>[2]:&nbsp;<a href=3D"https://github.com/sapio=
-lang/sapio">https://github.com/sapio-lang/sapio</a></div></body></html>=

--Apple-Mail-4AB29EF3-859C-4240-8AAE-8C045A8DFA40--