path: root/a1/58f2091a614ed99bddf122f4b155fb6f849bca

Return-Path: <antoine.riard@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id DD406C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 14 Nov 2022 02:21:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id B0B8640554
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 14 Nov 2022 02:21:29 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org B0B8640554
Authentication-Results: smtp4.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20210112 header.b=ShtEyYTv
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 smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id qEWEZ1H9Lx_Y
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 14 Nov 2022 02:21:28 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 526ED402D1
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com
 [IPv6:2607:f8b0:4864:20::d36])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 526ED402D1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 14 Nov 2022 02:21:28 +0000 (UTC)
Received: by mail-io1-xd36.google.com with SMTP id r81so7280265iod.2
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 13 Nov 2022 18:21:28 -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=gOFlkC6gfFT8ktl9N930A4w0qEQ2LjmCvBwD2HSZ/fQ=;
 b=ShtEyYTvtXFg0kjAnHGng0+SnEw9f4/AMR71Ifc2HQ86oaf3kusUSNlLkPgHZWnL6I
 z56I/vy+DrvhquAt4Uke/vWwLpZxP4eA3S5wG+2qM+2uRDiaKw5Ysmr5ZH8706QQXz88
 c9e/YHw4LA0qt9Wdn476lIKFh2fPyJIjCNEsQC2/+0Ubcuh0CYWG+kfM+Rxd5ckIU6Xz
 wXBExqqP9SHFkt90HlzgnsCFCVmp84BQAwxAsJQwiSzv88XAbtcyWlt95/6SHL/rntUA
 rrjyY73pn0JIMy7xEraLVrGzy+TYdxqaMijL32djJtFvYgi724/aLa9PSD33dfGqJamm
 z32w==
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=gOFlkC6gfFT8ktl9N930A4w0qEQ2LjmCvBwD2HSZ/fQ=;
 b=0OzARVJqrZ0eCksiVKhXB1Bs0iQ198gC6WBZ8+y4xz9SRfqKu6NCMD+dFMzRiKzvFZ
 U4j6ha6Ci2lhl58FCu2TzPuz6JX85XmBXNfFYVD+iVk7nTlxMOQf9LJWJUVLXsb8PxKd
 OT4YqpGLJPpjQCDh92U5PmXBc/OnVLIvWpdxtc6fRRKO6HvmEghlr2yC1MGqCwmBhlHg
 sElU4C0sWd7j4hDORz4Cr+T6eHr/YxnikelQ1gxvSKpTJ8Nc6ObNlv8dQUV6lLNibchX
 hDOSo599Z9z7dBtAayofCFwDD/XqjXEBVWNW4ivWw/GDrvgSa3sAdM0CISQ6wAH++nIN
 VNRw==
X-Gm-Message-State: ANoB5plF0aIFdkxMWt/gvW1gGJ9FHuLVHfiF1v80ccvFJ9/rgKd6BvXd
 Z2e+da4fmU95XI05/V4qamjgTzoDkeMRbF4rrx+b/EbVfbI=
X-Google-Smtp-Source: AA0mqf4b6Bf35pwZAwqyK9RWDxd1D/E2sCzXrH7sSJ9qIIlCA0y5J1tkBf9kZPC7vF05Odh1VMm8cnVE8RON2xjBrgY=
X-Received: by 2002:a6b:1416:0:b0:6bc:6a1c:eb26 with SMTP id
 22-20020a6b1416000000b006bc6a1ceb26mr4824897iou.64.1668392487078; Sun, 13 Nov
 2022 18:21:27 -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: Sun, 13 Nov 2022 21:21:16 -0500
Message-ID: <CALZpt+E0PSc_DD39E1-3hGYvpw3ok91Nc5DLTTh9FPdOKF_TYg@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000089cf5505ed64e562"
X-Mailman-Approved-At: Mon, 14 Nov 2022 02:55:39 +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: Mon, 14 Nov 2022 02:21:30 -0000

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

Reminder: this is happening this _upcoming_ Tuesday.

Looking forward to the first session, listening to everyone's thoughts
about what could be the scope discussed by this new community process:
anyprevout, recursive covenants, introspection, new malleability flags, ZK
rollups, new contracting protocols and many more ideas!

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.
>

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

<div dir=3D"ltr"><div><div><div>Reminder: this is happening this _upcoming_=
 Tuesday. <br><br></div>Looking forward to the first session, listening to =
everyone&#39;s thoughts about what could be the scope discussed by this new=
 community process: anyprevout, recursive covenants, introspection, new mal=
leability flags, ZK rollups, new contracting protocols and many more ideas!=
 <br><br></div>Best,<br></div>Antoine<br></div><br><div class=3D"gmail_quot=
e"><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">a=
ntoine.riard@gmail.com</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi list,<br><div><br>Af=
ter I have been asked offline the exact date when those meetings were actua=
lly starting, I&#39;m proposing Tuesday 15th November at 18:00 UTC, i.e 2 w=
eeks from now. Thinking about a monthly frequency for now (from my experien=
ce attending dlcspecs/lighnting specs meetings/core dev meetings in the pas=
t, 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 session [0].<br><br>Communication venue is #=
bitcoin-contracting-primitives-wg on Libera Chat [1]. Feel free to lurk alr=
eady and ask questions.<br><br>No consistent agenda beyond listening to eve=
ry attendee their expectations, ideas, subjects of interests they would lik=
e to see happening with this new covenants/contracting primitives R&amp;D p=
rocess.<br><br>If you have been working on a contracting protocols/side-cha=
ins/rollups/other use-cases that could benefit from extended Bitcoin contra=
cting primitives, feel free to open an issue there: <a href=3D"https://gith=
ub.com/ariard/bitcoin-contracting-primitives-wg/issues" target=3D"_blank">h=
ttps://github.com/ariard/bitcoin-contracting-primitives-wg/issues</a><br><b=
r>Let it know if you have more questions or feedback.<br><br>Cheers,<br>Ant=
oine<br><br>[0] It would be great to have a schedule inclusive of most time=
zones we can, 18:00 UTC might be too early for Asian and Oceanic ones. Late=
r, we start to be exclusive towards contributors in Eastern Europe.<br><br>=
[1] There have been more voices suggesting jitsi/audio-based meetings rathe=
r than IRC. It&#39;s a cool format too, though coming with trade-offs.<br><=
/div></div>
</blockquote></div>

--00000000000089cf5505ed64e562--