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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 4AD87C0011
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 24 Feb 2022 02:20:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 3216082F6F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 24 Feb 2022 02:20:40 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 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, FREEMAIL_FROM=0.001,
FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=protonmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id iq6dxqNkpurx
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 24 Feb 2022 02:20:39 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch
[185.70.40.132])
by smtp1.osuosl.org (Postfix) with ESMTPS id 67F7F82F6C
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 24 Feb 2022 02:20:39 +0000 (UTC)
Date: Thu, 24 Feb 2022 02:20:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1645669236;
bh=gwQ8Mc3VzW2hcd5L4U5EC43CwJpGvgZqWlXXv94MBbg=;
h=Date:To:From:Reply-To:Subject:Message-ID:In-Reply-To:References:
From:To:Cc:Date:Subject:Reply-To:Feedback-ID:Message-ID;
b=Rt94mzLn0mHgVOsUiGgLC6mnJC/1GNwMXD0DrbqfcBKWJH8ZfQ/8J/eTFvEQ8RIVc
rsK5NoCN5FDm+2l/P3aY3K3C+p+gPFDMffhdqnI7oKqVGTqI6FV9TCSBqUkG+qqXQZ
A8xMMtXN0KOuvJ8rgTSNF3nmQHbpU4Pbkl0bcGyZeCM1QDdxCxa9YewlHqaAw+F1tG
ZxmsxavYvqSoGo7QJZN45jahmxbH3yvpgB5tyOMOnvx8+tYDSn8OrTAN4oYNXwX8Wb
Xng02PTWlzWcr5y5jPbMOvPe+jL08tpAnx97ZjrEWiFD9ED/jv1bRHwUX35yaOWJ/O
kL9AjwyI94ShA==
To: Paul Sztorc <truthcoin@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <oeVo1wDV1iOMP1HnlySeSog59dmpYGvN83cGH_jutX0MdB8RInLa-CX2ArA_A0fexHAm6u9tUfrxjiUOskKGTLjjolRFFZUSV14RRpPTvFA=@protonmail.com>
In-Reply-To: <af77712d-fd9e-b8f3-8541-3edb3622150c@gmail.com>
References: <CAMZUoK=pkZuovtifBzdqhoyegzG+9hRTFEc7fG9nZPDK4KbU3w@mail.gmail.com>
<87leymuiu8.fsf@rustcorp.com.au>
<CAD5xwhgP2_51Dvar0f1tsMrCXZ61W9-HnLgR45D-54Oc7-X1ag@mail.gmail.com>
<0100017ee6472e02-037d355d-4c16-43b0-81d2-4a82b580ba99-000000@email.amazonses.com>
<i710HUIxNHIqCNhkh07dzlShyDp9ZkoEokw9ZBezCFvsk05ZUy5fXK1xx_IQifLh4f3RYb8FJM_MFm7hAaQFaUM3Jy3E8QhfSzkaogAu1Gs=@protonmail.com>
<af77712d-fd9e-b8f3-8541-3edb3622150c@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] Recursive covenant opposition,
or the absence thereof,
was Re: TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and
ANYPREVOUT
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: Thu, 24 Feb 2022 02:20:40 -0000
Good morning Paul, welcome back, and the list,
For the most part I am reluctant to add Turing-completeness due to the Prin=
ciple of Least Power.
We saw this play out on the web browser technology.
A full Turing-complete language was included fairly early in a popular HTML=
implementation, which everyone else then copied.
In the beginning, it had very loose boundaries, and protections against thi=
ngs like cross-site scripting did not exist.
Eventually, W3C cracked down and modern JavaScript is now a lot more sandbo=
xed than at the beginning --- restricting its power.
In addition, for things like "change the color of this bit when the mouse h=
overs it", which used to be implemented in JavaScript, were moved to CSS, a=
non-Turing-complete language.
The Principle of Least Power is that we should strive to use the language w=
ith *only what we need*, and naught else.
So I think for the most part that Turing-completeness is dangerous.
There may be things, other than Drivechain, that you might object to enabli=
ng in Bitcoin, and if those things can be implemented in a Turing-complete =
language, then they are likely implementable in recursive covenants.
That the web *started* with a powerful language that was later restricted i=
s fine for the web.
After all, the main use of the web is showing videos of attractive female h=
umans, and cute cats.
(WARNING: WHEN I TAKE OVER THE WORLD, I WILL TILE IT WITH CUTE CAT PICTURES=
.)
(Note: I am not an AI that seeks to take over the world.)
But Bitcoin protects money, which I think is more important, as it can be t=
raded not only for videos of attractive female humans, and cute cats, but o=
ther, lesser things as well.
So I believe some reticence towards recursive covenants, and other things i=
t may enable, is warranted,
Principle of Least Power exists, though admittedly, this principle was deve=
loped for the web.
The web is a server-client protocol, but Bitcoin is peer-to-peer, so it see=
ms certainly possible that Principle of Least Power does not apply to Bitco=
in.
As I understand it, however, the Principle of Least Power exists *precisely=
* because increased power often lets third parties do more than what was ex=
pected, including things that might damage the interests of the people who =
allowed the increased power to exist, or things that might damage the inter=
ests of *everyone*.
One can point out as well, that despite the problems that JavaScript introd=
uced, it also introduced GMail and the now-rich Web ecosystem.
Perhaps one might liken recursive covenants to the box that was opened by P=
andora.
Once opened, what is released cannot be put back.
Yet perhaps at the bottom of this box, is Hope?
Also: Go not to the elves for counsel, for they will say both no and yes.
Regards,
ZmnSCPxj
|
