path: root/1b/4db2ceed96dfd3de021c141aff2f6cfbb52da0

Return-Path: <antoine.riard@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 61387C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 15 Nov 2022 23:47:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 287F281E20
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 15 Nov 2022 23:47:53 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 287F281E20
Authentication-Results: smtp1.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20210112 header.b=lCuzT/X1
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 smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id HaCkcAFvaSNr
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 15 Nov 2022 23:47:52 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org C9D388188B
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com
 [IPv6:2607:f8b0:4864:20::12c])
 by smtp1.osuosl.org (Postfix) with ESMTPS id C9D388188B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 15 Nov 2022 23:47:51 +0000 (UTC)
Received: by mail-il1-x12c.google.com with SMTP id bp12so8294856ilb.9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 15 Nov 2022 15:47:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=7qdpqBwYhDz7wGjF31fUZqp+7plxJvxDS+eHcISVw2o=;
 b=lCuzT/X1MqNQENldRSZFaT/yAYNfZpQnuHpPDJjbRKRNbn2Pk5f4/ds1DSbVdPezRk
 dwZYVUcysNftMB1hIoumg0NAttob6HrJjHY/MqR4PGkRdnPVS73Li5dhKMVYp2+PsykP
 9ahAJi4nMT2UHYZfS67RF4zBImh1dJUR8ol3+EIh7eGqDqzDHnEvoYZe7Csz7zRE4Of2
 pmc0cprrfTzTL8pi8vdo87Yl61R3zK6oPbwtHnN1z2BNg+yN43jtFGd3yimGTcrmmsJt
 hJbaBPXkfaNEgiFwL1RlMyRLKNTvEebYUhiJKZ6NBN/AG3/HAUsIYe/Kfxp9HwIiBd1L
 pcbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=7qdpqBwYhDz7wGjF31fUZqp+7plxJvxDS+eHcISVw2o=;
 b=8IjBxR9Z3WOC5zlRsTFnkg4dTU+PgpndkR4GD1/qDxAhvEVZVCCfpT0xIOR+uEdA7S
 N5ts7710MtPzzo9rLdoYmABf15172T+8Sur/Z40AJf1O6cX/9fud52YrAfXKXH/9paqF
 g5gWZtJA+VFvblxkA1mj2PbF/+J2DszFxj50tpmimy36aHaX+NRylZs1XYfIJQbunsq4
 TctdQoA4m3ZanGrcXf+emyFP7X24Bk4tIGVwdcs3bGFbgNlxxprpHadliCjhZLg9pbTB
 7DUkdJ2zcURX4CghsBs1xf3pJDgYhZc9OELokPwc9paQBsHXsZFOuA3uqJYPzAg3nzec
 hgOA==
X-Gm-Message-State: ANoB5plO65q+bMlbLOzkBehjZGkFapnoQQEV89ohkRCFR2LTBGLpQfaP
 ov8hp0Dc4bjPTAxC2wrOzrEl1cpd+q3A1kgIgue/ecuY4hGygA==
X-Google-Smtp-Source: AA0mqf4ltQJRIEK9SYUNhn0UAlFcdHin4tmytfYzPqSiBwgw4RgH8eLllHTLrkTR3QZ6rkWtaA6uHNDrrfaLsKNYWxM=
X-Received: by 2002:a92:cc41:0:b0:300:e703:34b7 with SMTP id
 t1-20020a92cc41000000b00300e70334b7mr9580346ilq.250.1668556070712; Tue, 15
 Nov 2022 15:47:50 -0800 (PST)
MIME-Version: 1.0
References: <CALZpt+EygPsez0c84Yfmc6h+L7Ji8C3zE_E=EzPzLh4XWNHvZA@mail.gmail.com>
In-Reply-To: <CALZpt+EygPsez0c84Yfmc6h+L7Ji8C3zE_E=EzPzLh4XWNHvZA@mail.gmail.com>
From: Antoine Riard <antoine.riard@gmail.com>
Date: Tue, 15 Nov 2022 18:47:39 -0500
Message-ID: <CALZpt+GMGFor6xFUW-549gf2t1kmM1j+uNzK1JBVv18Q0VXi=A@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000e1fc1105ed8afb9d"
X-Mailman-Approved-At: Wed, 16 Nov 2022 00:28:09 +0000
Subject: Re: [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, 15 Nov 2022 23:47:53 -0000

--000000000000e1fc1105ed8afb9d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi list,

1st meeting did happen this afternoon with like ~10 attendees, we browsed
the covenant interests of everyone: state channels, universal settlement
layer, transaction introspection covenants, vaults/self-custody, MATT
covenants, logical label covenant like transaction inherited IDs,
congestion control, DLC and few more.

One of the goal of the process suggested by one of the attendee could be to
address "1) misunderstanding of the state of development and desire for
some covenant-style upgrade, 2) coordinating around goals, drawbacks and
overlap of different proposals and 3) helping to highlight consensus
building around the goals and mechanism to achieve them".

Next meeting aims to do a 360 degree panorama of all the known consistent
contracting primitives as well as the contracting protocols in an archiving
effort. If you have more contracting primitives to pin, feel free to
modify:
https://github.com/ariard/bitcoin-contracting-primitives-wg/tree/main/primi=
tives

Frequency schedule is for now every month, staying on the 3rd Tuesday of
every month. I'll announce them on time on the mailing list.

Meetings log available here:
https://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/meeti=
ngs/meetings-15-11.md

If you have more suggestions to improve the process, feel free to comment.

Best,
Antoine

Le lun. 31 oct. 2022 =C3=A0 20:47, Antoine Riard <antoine.riard@gmail.com> =
a
=C3=A9crit :

> 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 durin=
g
> 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 happeni=
ng
> 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.
>

--000000000000e1fc1105ed8afb9d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi list,<br><br>1st meeting did happen this afternoon with=
 like ~10 attendees, we browsed the covenant interests of everyone: state c=
hannels, universal settlement layer, transaction introspection covenants, v=
aults/self-custody, MATT covenants, logical label covenant like transaction=
 inherited IDs, congestion control, DLC and few more.<br><br>One of the goa=
l of the process suggested by one of the attendee could be to address &quot=
;1) misunderstanding of the state of development and desire for some covena=
nt-style upgrade, 2) coordinating around goals, drawbacks and overlap of di=
fferent proposals and 3) helping to highlight consensus building around the=
 goals and mechanism to achieve them&quot;.<br><br>Next meeting aims to do =
a 360 degree panorama of all the known consistent contracting primitives as=
 well as the contracting protocols in an archiving effort. If you have more=
 contracting primitives to pin, feel free to modify: <a href=3D"https://git=
hub.com/ariard/bitcoin-contracting-primitives-wg/tree/main/primitives">http=
s://github.com/ariard/bitcoin-contracting-primitives-wg/tree/main/primitive=
s</a><br><br>Frequency schedule is for now every month, staying on the 3rd =
Tuesday of every month. I&#39;ll announce them on time on the mailing list.=
<br><br>Meetings log available here: <a href=3D"https://github.com/ariard/b=
itcoin-contracting-primitives-wg/blob/main/meetings/meetings-15-11.md">http=
s://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/meetings/=
meetings-15-11.md</a><br><br>If you have more suggestions to improve the pr=
ocess, feel free to comment.<br><br>Best,<br>Antoine<br></div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0lun. 31 oct=
. 2022 =C3=A0=C2=A020:47, Antoine Riard &lt;<a href=3D"mailto:antoine.riard=
@gmail.com">antoine.riard@gmail.com</a>&gt; a =C3=A9crit=C2=A0:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi list,<b=
r><div><br>After I have been asked offline the exact date when those meetin=
gs were actually starting, I&#39;m proposing Tuesday 15th November at 18:00=
 UTC, i.e 2 weeks from now. Thinking about a monthly frequency for now (fro=
m my experience attending dlcspecs/lighnting specs meetings/core dev meetin=
gs in the past, weekly sounds too much, biweekly/monthly sounds better thou=
gh dunno yet good frequency).<br><br>If there is an incompatibility with an=
other public engineering meeting in the Bitcoin space, let it know. We can =
talk about a better schedule during the 1st session [0].<br><br>Communicati=
on venue is #bitcoin-contracting-primitives-wg on Libera Chat [1]. Feel fre=
e to lurk already and ask questions.<br><br>No consistent agenda beyond lis=
tening to every attendee their expectations, ideas, subjects of interests t=
hey would like to see happening with this new covenants/contracting primiti=
ves R&amp;D process.<br><br>If you have been working on a contracting proto=
cols/side-chains/rollups/other use-cases that could benefit from extended B=
itcoin contracting primitives, feel free to open an issue there: <a href=3D=
"https://github.com/ariard/bitcoin-contracting-primitives-wg/issues" target=
=3D"_blank">https://github.com/ariard/bitcoin-contracting-primitives-wg/iss=
ues</a><br><br>Let it know if you have more questions or feedback.<br><br>C=
heers,<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 Ocean=
ic ones. Later, we start to be exclusive towards contributors in Eastern Eu=
rope.<br><br>[1] There have been more voices suggesting jitsi/audio-based m=
eetings rather than IRC. It&#39;s a cool format too, though coming with tra=
de-offs.<br></div></div>
</blockquote></div>

--000000000000e1fc1105ed8afb9d--