path: root/51/3c256f63aae11819f3f8f22cdc1ba2bab8c9fe

Return-Path: <antoine.riard@gmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 73456C002B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  8 Feb 2023 02:00:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 4D7766107E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  8 Feb 2023 02:00:12 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 4D7766107E
Authentication-Results: smtp3.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20210112 header.b=Bvzr++VG
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 smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id I65JRNYSwX1c
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  8 Feb 2023 02:00:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 2ADF06100F
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com
 [IPv6:2607:f8b0:4864:20::131])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 2ADF06100F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  8 Feb 2023 02:00:11 +0000 (UTC)
Received: by mail-il1-x131.google.com with SMTP id z17so3617046ilm.7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 07 Feb 2023 18:00:11 -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=KzLNiijQH6hs6niIqHvsIjiUXuGvRSslCynJ9+a3RmE=;
 b=Bvzr++VGsHVdviv2ND6tvw7+Sm0d4qutLg1od0HCnZaqW6LchKSiI80mbpvurtk2yU
 JSml4ggqQGVsDPFETmORz8+vbDOkozTHePKF1InePNsJMtw7sGCU5aNklnXGs00gNobQ
 DzvIGBDh2H/OSM4Yn5Kb0rkZfgNrRvBJWBT4j+xztj2MooNZsbW/ZmgVj4/vUbQ8iSv2
 VGxQVpFLOdI0+BAaZs4Z9kwKoasmJ3yx+hpnxYtz02KrSg2JCf8GaFEjYI505MEF+sBV
 gJcnj6Am0Hsqwop4IroV6RAqnivFRg+/EWgZjHaGaKmFbPBfOe/rIUzND9wRFiz/HTdC
 6Bog==
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=KzLNiijQH6hs6niIqHvsIjiUXuGvRSslCynJ9+a3RmE=;
 b=OQmwgLueg6MY82vHKsoswVMCcjnvxVKiGfoCqlDBEcCvZm4vhxacwEeSNTRkpBQcMR
 LY9RmPzfN/Weov4oBn/cflcsY136ZY2sKB4utVre6S+P1/9SLBoG/ojGmItkpP6/5hig
 bATNNVrJw6BAHl5qzOtkfO298ZTLeqw90X1AO7MyTt0jDTe55XCpO7OiJvbLz9OWPDes
 PvJmlk74AKH349goCVlk712DS2C23OBpUozyp8SRcWKhR93l1OOzcgFQ3dS4ftwm+3iC
 1ivRlQasAznf9BKXbdv1IX8fZNjWS4c1p5bZy0ra3uTuvvVIOnYsQNW0jf+po/FWABaO
 7DsQ==
X-Gm-Message-State: AO0yUKX+lsLokF6bNUvjnReVTuYDCqDxF8yt3RQJERl+7KO5WTuHer98
 TcM3OrnzTfaRTl5J4gxvnaHvkMwcVah7nnYHmOTTtWVflONYkQ==
X-Google-Smtp-Source: AK7set89ZSzpUDD9B7zJ62+bvGPMBKi0SXTidFoeLYWhPtjnACi9cQtH4gCSsJAshHiNx2MUEZpOpFrF82SFbdf8yLc=
X-Received: by 2002:a05:6e02:8ad:b0:313:cc0d:27fc with SMTP id
 a13-20020a056e0208ad00b00313cc0d27fcmr3711781ilt.79.1675821610009; Tue, 07
 Feb 2023 18:00:10 -0800 (PST)
MIME-Version: 1.0
From: Antoine Riard <antoine.riard@gmail.com>
Date: Wed, 8 Feb 2023 01:59:59 +0000
Message-ID: <CALZpt+Ep+pSkO58eOrzM57EZCGi--iperhyiEtrGP83rLp5atA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000c58b6305f4269fe8"
X-Mailman-Approved-At: Wed, 08 Feb 2023 02:06:56 +0000
Subject: [bitcoin-dev] Bitcoin Contracting Primitives WG 4rd Meeting,
	Tuesday 21 Feb. 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: Wed, 08 Feb 2023 02:00:12 -0000

--000000000000c58b6305f4269fe8
Content-Type: text/plain; charset="UTF-8"

Hi list,

I'm proposing Tuesday 21st February at 18:00, i.e 2 weeks from now for the
4th Bitcoin contracting primitives WG meeting (the third Tuesday of
February month, as done previously).

As mentioned during the previous session, there is an issue if anyone would
like to propose an agenda topic in advance in an open fashion:
https://github.com/ariard/bitcoin-contracting-primitives-wg/issues/34

I would like to propose 2 topics for this upcoming meeting.

Firstly, ANYPREVOUT / "Eltoo", there has been a work in progress during the
last year for eltoo lightning channels [0]. I think there are still few
high-level open questions around fee-bumping and watchtowers, how the
proposal would benefit other off-chain constructions, how the proposal
works compared to other update mechanisms and a bunch of other things.

Secondly, if there is sufficient interest, setting up an open meatspace
event during S2 2023 or S1 2024. Meatspace events can be a great thing to
accelerate the development pace of contracting protocols. From my
experience in-person whiteboard sessions are highly valuable to sync on
complex subjects and it has been already evoked in the context of this
community process. Ideally, the event would piggyback on some existing
bitcoin conference. And I would see this as complementary to the other
bitcoin engineering meetings we've already scheduled, just open contracting
primitives R&D to a large set of people beyond the usual crowd contributing
already to Bitcoin Core [1].

If we have time remaining, we could listen to everyone blockers in their
contracting primitives/covenant research.

Communication venue is #bitcoin-contracting-primitives-wg on Libera Chat
IRC. Logs of the previous session are available here [2].

If you have any questions or feedback, I'm staying responsive.

Cheers,
Antoine

[0]
https://lists.linuxfoundation.org/pipermail/lightning-dev/2022-December/003788.html
[1] In term of janitorial role decentralization, I think it would be
valuable to have the event organization carried on by someone else reliable
other than myself. Contributed to CoreDev Zurich 2021 organisation, so I
can share the operational practices.
[2]
https://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/meetings/meetings-17-01.md

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

<div dir=3D"ltr">Hi list,<div><br></div><div>I&#39;m proposing Tuesday 21st=
 February at 18:00, i.e 2 weeks from now for the 4th Bitcoin contracting pr=
imitives WG meeting (the third Tuesday of February month, as done previousl=
y).</div><div><br></div><div>As mentioned during the previous session, ther=
e is an issue if anyone would like to propose an agenda topic in advance in=
 an open fashion:</div><div><a href=3D"https://github.com/ariard/bitcoin-co=
ntracting-primitives-wg/issues/34">https://github.com/ariard/bitcoin-contra=
cting-primitives-wg/issues/34</a><br></div><div><br></div><div>I would like=
 to propose 2 topics for this upcoming meeting.</div><div><br></div><div>Fi=
rstly, ANYPREVOUT / &quot;Eltoo&quot;, there has been a work in progress du=
ring the last year for eltoo lightning channels [0]. I think there are stil=
l few high-level open questions around fee-bumping and watchtowers, how the=
 proposal would benefit other off-chain constructions, how the proposal wor=
ks compared to other update mechanisms=C2=A0and a bunch of other things.</d=
iv><div><br></div><div>Secondly, if there is sufficient interest, setting u=
p an open meatspace event during S2 2023 or S1 2024. Meatspace events can b=
e a great thing to accelerate the development pace of contracting protocols=
. From my experience in-person whiteboard sessions are highly valuable to s=
ync on complex subjects and it has been already evoked in the context of th=
is community process. Ideally, the event would piggyback on some existing b=
itcoin conference. And I would see this as complementary to the other bitco=
in engineering meetings we&#39;ve already scheduled, just open contracting =
primitives R&amp;D to a large set of people beyond the usual crowd contribu=
ting already to Bitcoin Core [1].</div><div><br></div><div>If we have time =
remaining, we could listen to everyone blockers in their contracting primit=
ives/covenant research.</div><div><br></div><div>Communication venue is #bi=
tcoin-contracting-primitives-wg on Libera Chat IRC. Logs of the previous se=
ssion are available here [2].</div><div><br></div><div>If you have any ques=
tions or feedback, I&#39;m staying responsive.</div><div><br></div><div>Che=
ers,</div><div>Antoine</div><div><br></div><div>[0]=C2=A0<a href=3D"https:/=
/lists.linuxfoundation.org/pipermail/lightning-dev/2022-December/003788.htm=
l">https://lists.linuxfoundation.org/pipermail/lightning-dev/2022-December/=
003788.html</a></div><div>[1] In term of janitorial role decentralization, =
I think it would be valuable to have the event organization carried on by s=
omeone else reliable other than myself. Contributed to CoreDev Zurich 2021 =
organisation, so I can share the operational practices.</div><div>[2]=C2=A0=
<a href=3D"https://github.com/ariard/bitcoin-contracting-primitives-wg/blob=
/main/meetings/meetings-17-01.md">https://github.com/ariard/bitcoin-contrac=
ting-primitives-wg/blob/main/meetings/meetings-17-01.md</a></div><div><br><=
/div><div><br></div><div><br></div></div>

--000000000000c58b6305f4269fe8--