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
|
Return-Path: <bram@chia.net>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 33266C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 Jul 2022 18:23:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 0D8614048C
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 Jul 2022 18:23:04 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 0D8614048C
Authentication-Results: smtp2.osuosl.org;
dkim=pass (2048-bit key) header.d=chia.net header.i=@chia.net
header.a=rsa-sha256 header.s=google header.b=WPayNPCq
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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id ryrW5RuLOlB1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 Jul 2022 18:23:03 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 1A9DF400B9
Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com
[IPv6:2607:f8b0:4864:20::1133])
by smtp2.osuosl.org (Postfix) with ESMTPS id 1A9DF400B9
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 Jul 2022 18:23:02 +0000 (UTC)
Received: by mail-yw1-x1133.google.com with SMTP id
00721157ae682-31d85f82f0bso90217237b3.7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 Jul 2022 11:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chia.net; s=google;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=2xN9Ral2j8qeyffJcKPX9/0d0zBsyyTU2H5jT2r19A8=;
b=WPayNPCqzHBE6GspK10hRhjYyG+231Zk+YiAfCyTxC7o1TbMEe8Ax1cvjk7f5T3Kw+
HeDn1CdmdmkSAoOTtQkxqnVcGkovtP1HgYpBVj2UmrKIsdcJroc3p3wopzDd04SiGaTl
PFc9T09Hw1FWI47fVlpywoEURS6608fXUiGR3wm465YP3XogamX4LduLMO0lFjYN4n/L
PmGrvqW+05Ivi63g/R6NjIzL2/jOW5fdpC/DQ0MKVMYUVnqX7+mMPawpF/bG0ILEMX9u
nMtmrGj/pWJm/pAFNBNLfY/WUtklwoIpqrWLCD3I/SwevqfPws7pt5OvbTSOwoCC7UQL
FZOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=2xN9Ral2j8qeyffJcKPX9/0d0zBsyyTU2H5jT2r19A8=;
b=tAJFebdvqIR+EmPWBewW6rWh3JCbUkkSmK78YOoc0qvrKLo+rShLeuBoYY9AZ3G2SB
OBhmIE7BMt9VoWthoDeKWxvaczcgbU3grqw2bMBNhF3JAuFQd8WyV29HHS0KAbXAgfGA
apG3MAx/X/DS8eOi8SSE2g+UaD3tPai8zAYGFbiIKUzriVeh3pdXQQgOAnx6LwFoiwDq
LeOgOgeknZYeJcP3CIxHDOb09lD+4xX38HewOrAOxAlbZ3YA8AWn9caoqNxLNk2YcAHI
9GYAbWD5J5O/OVniDQ16ART343sRR2nqAct4rfeLDTHt8K04uXj7J/5yrOm0enVHT+iW
isZQ==
X-Gm-Message-State: AJIora+lqP/Rrg2pKLLq3+Z7KdRRZ3AOVcAliaD8M80fUSUuwqefyeNV
2wSdrr4KmK1dKOKzKFwyh1311PMIzY6Sh8zXmch4Jg==
X-Google-Smtp-Source: AGRyM1sXu+foyUXekc+r/U33jT0Q1HsBwOlqt5+tYk6RlCuVYzR/VdEZamClgfZPPZ3qubke7YUz90woUitEOqAOTJA=
X-Received: by 2002:a0d:e613:0:b0:31e:5fa4:f83c with SMTP id
p19-20020a0de613000000b0031e5fa4f83cmr7283646ywe.91.1658686981875; Sun, 24
Jul 2022 11:23:01 -0700 (PDT)
MIME-Version: 1.0
References: <CALZpt+FhpZETHP8UpDGgw-Wg=m4Hxm8y9XZ9kXYgmt90_6Zt6w@mail.gmail.com>
In-Reply-To: <CALZpt+FhpZETHP8UpDGgw-Wg=m4Hxm8y9XZ9kXYgmt90_6Zt6w@mail.gmail.com>
From: Bram Cohen <bram@chia.net>
Date: Sun, 24 Jul 2022 11:22:51 -0700
Message-ID: <CAHUJnBDu+PNvER-FmpT8593vX-wAZ1oPWJjQaJ=d7Y4pso_Txw@mail.gmail.com>
To: Antoine Riard <antoine.riard@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000005945b305e49128b4"
X-Mailman-Approved-At: Sun, 24 Jul 2022 18:34:04 +0000
Subject: Re: [bitcoin-dev] On a new community process to specify covenants
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: Sun, 24 Jul 2022 18:23:04 -0000
--0000000000005945b305e49128b4
Content-Type: text/plain; charset="UTF-8"
On Wed, Jul 20, 2022 at 2:46 PM Antoine Riard via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Indeed this range has grown wild. Without aiming to be exhaustive (I'm
> certainly missing some interesting proposals lost in the abyss of
> bitcointalk.org), we can mention the following use-cases: multi-party
> stateful contracts [11], congestion trees [12], payment pools [13], "eltoo"
> layered commitments [14], programmable vaults [15], multi-events contracts
> [16], blockchain-as-oracle bets [17], spacechains [18], trustless
> collateral lending [19], ...
>
The big question you missed is whether capabilities are in scope for a
covenants proposal. In particular, vaults work a lot better when payments
to them are immediately locked up in the vault rather than it having to do
a step to accept them first.
--0000000000005945b305e49128b4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jul 20, 2022 at 2:46 PM Antoine R=
iard via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundatio=
n.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
dir=3D"ltr">Indeed this range has grown wild. Without aiming to be exhaust=
ive (I'm certainly missing some interesting proposals lost in the abyss=
of <a href=3D"http://bitcointalk.org" target=3D"_blank">bitcointalk.org</a=
>), we can mention the following use-cases: multi-party stateful contracts =
[11], congestion trees [12], payment pools [13], "eltoo" layered =
commitments [14], programmable vaults [15], multi-events contracts [16], bl=
ockchain-as-oracle bets [17], spacechains [18], trustless collateral lendin=
g [19], ...<br></div></blockquote><div><br></div><div>The big question you =
missed is whether capabilities are in scope for a covenants proposal. In pa=
rticular, vaults work a lot better when payments to them are immediately lo=
cked up in the vault rather than it having to do a step to accept them firs=
t.</div></div></div>
--0000000000005945b305e49128b4--
|
