summaryrefslogtreecommitdiff
path: root/ef/98c0d9ebaa7eb09ec3b3910fca124bea3ac5c4
blob: b1e82f51747db6f3fe383bac81ae57e05ef7c35e (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
Return-Path: <prayank@tutanota.de>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 7DA52C001A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 26 Feb 2022 07:47:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 65F9C60B1D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 26 Feb 2022 07:47:18 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001,
 RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
 SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=tutanota.de
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id er9vpQcnDrJc
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 26 Feb 2022 07:47:17 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 29F4C60B1A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 26 Feb 2022 07:47:16 +0000 (UTC)
Received: from w3.tutanota.de (unknown [192.168.1.164])
 by w1.tutanota.de (Postfix) with ESMTP id F2696FBF4C9;
 Sat, 26 Feb 2022 07:47:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1645861634; 
 s=s1; d=tutanota.de;
 h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender;
 bh=IH0ob6YNHjK6AvYK5VlxG9fUF+tuNkFvMD/qoC+S2o4=;
 b=0OcCS8jHt4UCHmZLP5O1ObuzLCSH10hWqZc+QmSQwoihW5KoPtOFa0S4m/P94hGL
 QdhDyyccqPBLKq+QFzhURdhMW8E6JeLkXdEJzQ7CeFkdfnDkvTS/u057xBm9PvfZ+6b
 Mr1ETjj0ypMepvyG9NFch6cVAsTkpRIOZuCnPFIgKW9oQrrB9hMN0AYzsYtXHBPcH5L
 OzcTxIzPLgmi8ZW7GpQSjeK/jem7TIvQpgk1fdDkTMfhkaX7o/0wIs4aLl8Rli61koq
 C6wQmICo7Xcid4CB/KJBA5Z5rDXLFfoegt7Aaf+AKwuIfVmitp19ChTu9bP6lEUGbDO
 hKPe7pF9oA==
Date: Sat, 26 Feb 2022 08:47:14 +0100 (CET)
From: Prayank <prayank@tutanota.de>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <MwozrvU--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="----=_Part_321589_1387632195.1645861634979"
X-Mailman-Approved-At: Sat, 26 Feb 2022 08:34:24 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
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: Sat, 26 Feb 2022 07:47:18 -0000

------=_Part_321589_1387632195.1645861634979
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Good morning ZmnSCPxj,

> Of course, I know of no such technique, but given that a technique (Drivechains) which before would have required its own consensus change, turns out to be implementable inside recursive covenants, then I wonder if there are other things that would have required their own consensus change that are now *also* implementable purely in recursive covenants.


Agree. I would be interested to know what is NOT possible once we have recursive covenants.

> if there is *now* consensus that Drivechains are not bad, go ahead, add recursive covenants (but please can we add `SIGHASH_NOINPUT` and `OP_CTV` first?)


Agree and I think everything can be done in separate soft forks.



-- 
Prayank

A3B1 E430 2298 178F

------=_Part_321589_1387632195.1645861634979
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=3DUTF-8=
">
  </head>
  <body>
<div>Good morning ZmnSCPxj,<br></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">&gt; Of course, I know of no such technique, but given that a tec=
hnique (Drivechains) which before would have required its own consensus cha=
nge, turns out to be implementable inside recursive covenants, then I wonde=
r if there are other things that would have required their own consensus ch=
ange that are now *also* implementable purely in recursive covenants.<br></=
div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">Agree. I would be interested to know what is NOT possible once we have r=
ecursive covenants.<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">=
&gt; if there is *now* consensus that Drivechains are not bad, go ahead, ad=
d recursive covenants (but please can we add `SIGHASH_NOINPUT` and `OP_CTV`=
 first?)<br></div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><=
div dir=3D"auto">Agree and I think everything can be done in separate soft =
forks.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div di=
r=3D"auto"><br></div><div><br></div><div>-- <br></div><div>Prayank<br></div=
><div><br></div><div dir=3D"auto">A3B1 E430 2298 178F<br></div>  </body>
</html>

------=_Part_321589_1387632195.1645861634979--