Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 39E5DC002B for ; Tue, 21 Feb 2023 00:41:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 14E366100B for ; Tue, 21 Feb 2023 00:41:02 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 14E366100B 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=j+xOhw1O 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 2lHv55HvXBiC for ; Tue, 21 Feb 2023 00:41:01 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org E05BF60F2E Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) by smtp3.osuosl.org (Postfix) with ESMTPS id E05BF60F2E for ; Tue, 21 Feb 2023 00:41:00 +0000 (UTC) Received: by mail-io1-xd2c.google.com with SMTP id d16so1475576ion.13 for ; Mon, 20 Feb 2023 16:41:00 -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=gKlgduTJGBz1oW4erEd0eMDwiV5zRX3i1GPZoURQ/r0=; b=j+xOhw1OL6B5fXWQusDgtAZAi7kXiMsY+FnpnzQF8I70DzA+VSwKLZ7oqRrJOLjhJj +ezXR2AFtiWgbE67T+ZCeI9Zy1HywmYYuPMiYXFBoJf0SbYfMa0bTqSsaKzWAdBOEuyl RbK6vCPaJVb61C1Gu/tMFe6t5MtzB/LUHoK7xPbsVge4fdLV5aEeJcDnI01abRYdtqTH k9mlfKMLEoJ7Bn3Rji615luhdOBmP3aE1DEv7RER06j+AQz5w9o/8cHgKj9S/aGX8lUq Duhow6KLlp1jjAWZSLSkb4YgltqP6anLEUEYUkJ6VXfnD3+/YuOYqGPwGg31DX8H048U 6ubg== 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=gKlgduTJGBz1oW4erEd0eMDwiV5zRX3i1GPZoURQ/r0=; b=AW3L4MTo50kxYr4Nvl1xcQt3wE/IsZ7h7ZsSS9cX+wcj6qWVZMJ6Hp1ToNHbd4ItPY xrvhKkSWXTbLuxr2a67r5znTALYnUT2xiUOgAeVVZFqA72k/JQ4b41rDSkwQWKl+fn6r 1xHC7jo7I9qS+vAcKe3SIqfEXfv+VP4NhjnCgLGPq0x+lNdvKxJ25IGWap1RZtEAfqi6 vWbRMAk/6EKHfvylGE4Ge/InWmRPrU1dmdG8rzTwgNWIMfQpmyfhH+OhtGGIa5Ny2G4Q U8HC1DXDKWmhGteZklA2j62++0srJD1ssvumiObus7FECBZ6LXAusVJchdajifeX09fh hikg== X-Gm-Message-State: AO0yUKX5g5dkUP5twjM0ZV3RERX28DR0h4OOximi3t4jlmP/T1ymTcJN S1rPRqB9Tj5Wo6yfM0+OrF4zG7ePF4genhC7QzNu88MmyWc= X-Google-Smtp-Source: AK7set80dKKwoIVHJa0yzSvgXuHFYcZ6TLOQ5zF48zblp1bmkCCXaGheKzss8SE+b23jJrSkDHF/jzWnqYKxP3xK5E4= X-Received: by 2002:a5d:88ce:0:b0:71a:1e2a:e12 with SMTP id i14-20020a5d88ce000000b0071a1e2a0e12mr644005iol.82.1676940059704; Mon, 20 Feb 2023 16:40:59 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Antoine Riard Date: Tue, 21 Feb 2023 00:40:48 +0000 Message-ID: To: Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000091829205f52b087e" X-Mailman-Approved-At: Tue, 21 Feb 2023 00:45:46 +0000 Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2023 00:41:02 -0000 --00000000000091829205f52b087e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Reminder: this is happening this _upcoming_ Tuesday. Looking forward to the fourth session to roam over things like anyprevout, the annex, vault primitive, annexcarrier! Issue opened if anyone would like to propose an agenda topic: https://github.com/ariard/bitcoin-contracting-primitives-wg/issues/34 Best, Antoine Le mer. 8 f=C3=A9vr. 2023 =C3=A0 01:59, Antoine Riard a =C3=A9crit : > Hi list, > > I'm proposing Tuesday 21st February at 18:00, i.e 2 weeks from now for th= e > 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 f= ew > 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 contracti= ng > primitives R&D to a large set of people beyond the usual crowd contributi= ng > 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/0= 03788.html > [1] In term of janitorial role decentralization, I think it would be > valuable to have the event organization carried on by someone else reliab= le > 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/mee= tings/meetings-17-01.md > > > > --00000000000091829205f52b087e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Reminder: this is happening this _upcoming_ Tuesday.
<= br>
Looking forward to the fourth session to roam over things lik= e anyprevout, the annex, vault primitive, annexcarrier!

Issue opened if anyone would like to propose an agenda topic:
https://github.com/ariard/bitcoin-contracting-primitives-wg/issue= s/34

Best,
Antoine
Le=C2=A0= mer. 8 f=C3=A9vr. 2023 =C3=A0=C2=A001:59, Antoine Riard <antoine.riard@gmail.com> a =C3=A9crit=C2= =A0:
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 Fe= bruary month, as done previously).

As mentioned du= ring the previous session, there is an issue if anyone would like to propos= e an agenda topic in advance in an open fashion:

I would like to propose 2 topics for t= his upcoming meeting.

Firstly, ANYPREVOUT / "= Eltoo", there has been a work in progress during the last year for elt= oo lightning channels [0]. I think there are still few high-level open ques= tions around fee-bumping and watchtowers, how the proposal would benefit ot= her off-chain constructions, how the proposal works compared to other updat= e mechanisms=C2=A0and a bunch of other things.

Sec= ondly, 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 acceler= ate the development pace of contracting protocols. From my experience in-pe= rson whiteboard sessions are highly valuable to sync on complex subjects an= d it has been already evoked in the context of this community process. Idea= lly, the event would piggyback on some existing bitcoin conference. And I w= ould see this as complementary to the other bitcoin engineering meetings we= 've already scheduled, just open contracting primitives R&D to a la= rge set of people beyond the usual crowd contributing already to Bitcoin Co= re [1].

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

Communication venue is #bitcoin-contracting-primitiv= es-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

[1] In term of janitorial role decentralization, I think = it would be valuable to have the event organization carried on by someone e= lse reliable other than myself. Contributed to CoreDev Zurich 2021 organisa= tion, so I can share the operational practices.
--00000000000091829205f52b087e--