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
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
|
Return-Path: <antoine.riard@gmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id C2AA5C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Jan 2023 00:26:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id AB47040443
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Jan 2023 00:26:16 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org AB47040443
Authentication-Results: smtp2.osuosl.org;
dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
header.a=rsa-sha256 header.s=20210112 header.b=NygxKl9m
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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,
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 wy-STc9eRMQY
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Jan 2023 00:26:15 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 90DA240292
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com
[IPv6:2607:f8b0:4864:20::d2c])
by smtp2.osuosl.org (Postfix) with ESMTPS id 90DA240292
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 6 Jan 2023 00:26:15 +0000 (UTC)
Received: by mail-io1-xd2c.google.com with SMTP id r72so84831iod.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 05 Jan 2023 16:26:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
:date:message-id:reply-to;
bh=RzxwNYeMjmQvy3PKmQBXwozMwAJsZECtwuBKS5UYOoI=;
b=NygxKl9mvE5DQtkrwowBpg/PM7J5jpnf/oGkVZ7KR4Dva6OpDPZSZN3g/hjrG35u/r
XjQGeBIN6+yIfXYJ+fakWDzR66sZmbHoSYuDjYo9FRFN91M+SicOHcM5tIpBW24SLbl7
13IWcP1qUCqQpR2kniLb/dPG6NI1LNDMUSOFeOjM2ppl4oEvYI9D5YrlGA2HhB4PQFNi
oGkJHQzRit7x+W1qmvO3C/7KQ8DSYuVkb7zITEPNIU8FcGKl9b1AQ9CqSvWkblLHAlCz
nEBWifsXqsR10NC6ytVxRPo/G03oFTEO9g5hSzemhfwulTAt1k8SVKY3shsGS1OfViwO
VNMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=to:subject:message-id:date:from:mime-version:x-gm-message-state
:from:to:cc:subject:date:message-id:reply-to;
bh=RzxwNYeMjmQvy3PKmQBXwozMwAJsZECtwuBKS5UYOoI=;
b=jkdp+8tEbMUAoGSXmD4v7QXIx1ENXwYz4AkdpZNwfr2Z1z1c2h/FA9HZ++DDHuvnXf
4Yd+1NHqjBzym7Dck4TxmGkIDahENltRvIGvjtW9c3sms1LhtMe+aVGA5jNnHMSBZ+9Z
ika8PEOL5KfqDoyDM6NUNnCvHhVNSyGHtiULHCpaptLH0ZNMkSxH7txBEYxa8Zku1lUp
VResWEfniziXGG2L7fRso4yF7WVecAa8QXnXt616jjW+vW5iQJtEbfaM4D8703ozJjlL
qfRTgxPqQO5Rni2bkC2W3D/+nPzh+hmyoKBHUOnQCeurQqJtsduj+U0bbwsvfDmMaBS/
PjqQ==
X-Gm-Message-State: AFqh2kr3sNohr6Ue6DQWtbszdFk3VAWlIbAQGPynSKT8RV2DUuRVEI9v
xBbSIfOTmiz9XdS1ANMj1+QLt36Fj6U1yX8UW260hr/p/DA=
X-Google-Smtp-Source: AMrXdXuyj0QzgJYvaPPEKIdKun7ZZp/+SO6CX/YTMRI5NkzHFeYPXc93w9AUwGhJLPbEo0GJLbc7M4d/mNBHNxUg5xc=
X-Received: by 2002:a5e:850f:0:b0:6ec:f27e:58a5 with SMTP id
i15-20020a5e850f000000b006ecf27e58a5mr4241048ioj.15.1672964774449; Thu, 05
Jan 2023 16:26:14 -0800 (PST)
MIME-Version: 1.0
From: Antoine Riard <antoine.riard@gmail.com>
Date: Thu, 5 Jan 2023 19:26:03 -0500
Message-ID: <CALZpt+Eou=m9LnZfZoxfZcQLs7UL5Te53whNgYO1fro05iSvDw@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000001a586305f18d773e"
X-Mailman-Approved-At: Fri, 06 Jan 2023 00:28:59 +0000
Subject: [bitcoin-dev] Bitcoin Contracting Primitives WG 3rd Meeting,
Tuesday 17 Jan. 18:00 UTC
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: Fri, 06 Jan 2023 00:26:16 -0000
--0000000000001a586305f18d773e
Content-Type: text/plain; charset="UTF-8"
Hi list,
I'm proposing Tuesday 17th January at 18:00 UTC, i.e week from now for the
3rd Bitcoin contracting primitives WG meeting (the third Tuesday of January
month, as done previously).
As a soft proposal for an agenda, it would be to start with the leftover of
the last meeting agenda. Namely, roaming over all the contracting protocol
and use-case, to ensure there is exhaustivity of the R&D effort w.r.t known
ideas issued by the community during the past years. If you have been
working on a use-case, and it's missing in the current listing, feel free
to open a PR or bump me to do so (still same with primitives themselves
ofc).
The second part could be to take time to listen to everyone blockers in
their contracting primitives/covenant research.
About the R&D effort, one of my personal goal for the coming year would be
to nurture some websites, with the archive material progressively gathered
in the repository. The website would present the contracting protocol
research according to the best engineering/scientific
standards and ensure ideas neutrality. Ideally, it would enable collection
of feedback on dimensions like privacy or economic scaling from the Bitcoin
community of stakeholders at large, with Pretty Graphics (tm).
Beyond, pursuing a "decentralized" spirit, looking forward to starting
rotating meetings host during the year, as we're doing with BOLTs where
it's rotating between Lightning implementations contributors. If you're
interested in hosting one of the monthly meetings, feel free to open an
issue against the repository or bump me.
Communication venue is #bitcoin-contracting-primitives-wg on Libera Chat.
Logs of the previous session are available here [0].
Let it know if you have more questions or feedback.
Cheers,
Antoine
[0]
https://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/meetings/meetings-20-12.md
--0000000000001a586305f18d773e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi list,<br><br>I'm proposing Tuesday 17th January at =
18:00 UTC, i.e week from now for the 3rd Bitcoin contracting primitives WG =
meeting (the third Tuesday of January month, as done previously).<br><br>As=
a soft proposal for an agenda, it would be to start with the leftover of t=
he last meeting agenda. Namely, roaming over all the contracting protocol a=
nd use-case, to ensure there is exhaustivity of the R&D effort w.r.t kn=
own ideas issued by the community during the past years. If you have been w=
orking on a use-case, and it's missing in the current listing, feel fre=
e to open a PR or bump me to do so (still same with primitives themselves o=
fc).<br><br>The second part could be to take time to listen to everyone blo=
ckers in their contracting primitives/covenant research.<br><br>About the R=
&D effort, one of my personal goal for the coming year would be to nurt=
ure some websites, with the archive material progressively gathered in the =
repository. The website would present the contracting protocol research acc=
ording to the best engineering/scientific<br>standards and ensure ideas neu=
trality. Ideally, it would enable collection of feedback on dimensions like=
privacy or economic scaling from the Bitcoin community of stakeholders at =
large, with Pretty Graphics (tm).<br><br>Beyond, pursuing a "decentral=
ized" spirit, looking forward to starting rotating meetings host durin=
g the year, as we're doing with BOLTs where it's rotating between L=
ightning implementations contributors. If you're interested in hosting =
one of the monthly meetings, feel free to open an issue against the reposit=
ory or bump me.<br><br>Communication venue is #bitcoin-contracting-primitiv=
es-wg on Libera Chat. Logs of the previous session are available here [0].<=
br><br>Let it know if you have more questions or feedback.<br><br>Cheers,<b=
r>Antoine<br><br>[0] <a href=3D"https://github.com/ariard/bitcoin-contracti=
ng-primitives-wg/blob/main/meetings/meetings-20-12.md">https://github.com/a=
riard/bitcoin-contracting-primitives-wg/blob/main/meetings/meetings-20-12.m=
d</a><br></div>
--0000000000001a586305f18d773e--
|
