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
|
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 086EBC002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Nov 2022 00:47:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id C3BCA400CC
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Nov 2022 00:47:31 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org C3BCA400CC
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=qp+FH5OK
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 uTjFyZR2MwFW
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Nov 2022 00:47:30 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org B26DE400BB
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com
[IPv6:2607:f8b0:4864:20::d29])
by smtp2.osuosl.org (Postfix) with ESMTPS id B26DE400BB
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Nov 2022 00:47:30 +0000 (UTC)
Received: by mail-io1-xd29.google.com with SMTP id e189so384992iof.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 31 Oct 2022 17:47:30 -0700 (PDT)
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=7aXGcXZffHub6Sm7vAAli8BmthTzpA/vjMjNuYB/EdU=;
b=qp+FH5OKVld4qPbqYMaB22WgBibmMgQuUzmztEYHMF5rLlXe+6gM5Af3iDUj5IAEQJ
C+BO9bVYKGc+gvGMhVT/xB+2XRIeWBEB9piZzRDt6So/S5XOQdWXTlyhsM4JtwOJ7pic
FJB9uTeqZ8EbuDw0ssy8yhp36wK2bp+uaMGD3Tv7Pa2zCsIgvr1dbtzwsA+q96AUIedr
OT8SJwa8uEUPms/vAW8Q/CzfiJRu5a0KBjS1LHUMdAKsKRdx7fHFL8JFJmmL7VAnA2FO
vepuY35R2QwpqGh1gv3pHuWhdfENhBxorRu3zU+quFYoEk6yqKSQzM3dl6l4o3B6JMZ9
cgtw==
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=7aXGcXZffHub6Sm7vAAli8BmthTzpA/vjMjNuYB/EdU=;
b=z2pFHp3Z7baMlff4YxJXlRc/M49NOt2pH65n8aW11wcZVqTzsbHj8mecBJE90GLstp
Hz4bmtTcqs89yfVIop6WF4RnpkIww+BmrTk655WPjjEEwWyOg6RqoCulxTd/uXNHN1qN
Mdn5rgaVfBhxvWhT4IqbGs4Yo7ut9PXb2pbizLTCJxgMnDjxUVLaSal28RG3s9Lp56yC
qnG0elGXMHuA2kx71bgJ8ewt+3ryzWHeDUpTq3Ffo3FjSLsdypeb2hCJY4sR02m8scx9
3wjr1sI4xQac4B+CMmT6bCljVsIMzMxLP5iiZXN7o4hcso9yfGCwnfv0JGnCQljF7qf1
/nWw==
X-Gm-Message-State: ACrzQf0Xrh9bUwl+34dMwZLQOp6UmQ/jKaW5axeySUtxTazPVybVF8TP
yu+r0CT5OcMjAkwx2MIxmom3xr86QhKRq+tE4KNPk5v7UpO1Ncgl
X-Google-Smtp-Source: AMsMyM6tO/0ajCVben70ioz4Y2bxH7FNWcoWDzz+cRSv0mSJqDcs2DuPdConL+vnOwnhVnBmskijS6j03qiA9TM3aZA=
X-Received: by 2002:a05:6638:31c2:b0:363:496e:b5a1 with SMTP id
n2-20020a05663831c200b00363496eb5a1mr9874499jav.237.1667263649549; Mon, 31
Oct 2022 17:47:29 -0700 (PDT)
MIME-Version: 1.0
From: Antoine Riard <antoine.riard@gmail.com>
Date: Mon, 31 Oct 2022 20:47:18 -0400
Message-ID: <CALZpt+EygPsez0c84Yfmc6h+L7Ji8C3zE_E=EzPzLh4XWNHvZA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000009413ab05ec5e1127"
X-Mailman-Approved-At: Tue, 01 Nov 2022 03:01:14 +0000
Subject: [bitcoin-dev] Bitcoin Contracting Primitives WG 1st Meeting,
Tuesday 15 Nov. 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: Tue, 01 Nov 2022 00:47:32 -0000
--0000000000009413ab05ec5e1127
Content-Type: text/plain; charset="UTF-8"
Hi list,
After I have been asked offline the exact date when those meetings were
actually starting, I'm proposing Tuesday 15th November at 18:00 UTC, i.e 2
weeks from now. Thinking about a monthly frequency for now (from my
experience attending dlcspecs/lighnting specs meetings/core dev meetings in
the past, weekly sounds too much, biweekly/monthly sounds better though
dunno yet good frequency).
If there is an incompatibility with another public engineering meeting in
the Bitcoin space, let it know. We can talk about a better schedule during
the 1st session [0].
Communication venue is #bitcoin-contracting-primitives-wg on Libera Chat
[1]. Feel free to lurk already and ask questions.
No consistent agenda beyond listening to every attendee their expectations,
ideas, subjects of interests they would like to see happening with this new
covenants/contracting primitives R&D process.
If you have been working on a contracting
protocols/side-chains/rollups/other use-cases that could benefit from
extended Bitcoin contracting primitives, feel free to open an issue there:
https://github.com/ariard/bitcoin-contracting-primitives-wg/issues
Let it know if you have more questions or feedback.
Cheers,
Antoine
[0] It would be great to have a schedule inclusive of most timezones we
can, 18:00 UTC might be too early for Asian and Oceanic ones. Later, we
start to be exclusive towards contributors in Eastern Europe.
[1] There have been more voices suggesting jitsi/audio-based meetings
rather than IRC. It's a cool format too, though coming with trade-offs.
--0000000000009413ab05ec5e1127
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi list,<br><div><br>After I have been asked offline the e=
xact date when those meetings were actually starting, I'm proposing Tue=
sday 15th November at 18:00 UTC, i.e 2 weeks from now. Thinking about a mon=
thly frequency for now (from my experience attending dlcspecs/lighnting spe=
cs meetings/core dev meetings in the past, weekly sounds too much, biweekly=
/monthly sounds better though dunno yet good frequency).<br><br>If there is=
an incompatibility with another public engineering meeting in the Bitcoin =
space, let it know. We can talk about a better schedule during the 1st sess=
ion [0].<br><br>Communication venue is #bitcoin-contracting-primitives-wg o=
n Libera Chat [1]. Feel free to lurk already and ask questions.<br><br>No c=
onsistent agenda beyond listening to every attendee their expectations, ide=
as, subjects of interests they would like to see happening with this new co=
venants/contracting primitives R&D process.<br><br>If you have been wor=
king on a contracting protocols/side-chains/rollups/other use-cases that co=
uld benefit from extended Bitcoin contracting primitives, feel free to open=
an issue there: <a href=3D"https://github.com/ariard/bitcoin-contracting-p=
rimitives-wg/issues">https://github.com/ariard/bitcoin-contracting-primitiv=
es-wg/issues</a><br><br>Let it know if you have more questions or feedback.=
<br><br>Cheers,<br>Antoine<br><br>[0] It would be great to have a schedule =
inclusive of most timezones we can, 18:00 UTC might be too early for Asian =
and Oceanic ones. Later, we start to be exclusive towards contributors in E=
astern Europe.<br><br>[1] There have been more voices suggesting jitsi/audi=
o-based meetings rather than IRC. It's a cool format too, though coming=
with trade-offs.<br></div></div>
--0000000000009413ab05ec5e1127--
|
