path: root/cf/a25c341d70513627f737a1434234c5f463f51b

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 9D055C0070
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 20 Dec 2022 02:35:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 44C3F40921
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 20 Dec 2022 02:35:18 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 44C3F40921
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=jmyiiBPq
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 h--Krh1F-KwQ
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 20 Dec 2022 02:35:16 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org C8F23408ED
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com
 [IPv6:2607:f8b0:4864:20::d2a])
 by smtp4.osuosl.org (Postfix) with ESMTPS id C8F23408ED
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 20 Dec 2022 02:35:16 +0000 (UTC)
Received: by mail-io1-xd2a.google.com with SMTP id 3so5716051iou.12
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 19 Dec 2022 18:35:16 -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=k9r60rztpKam0KxapGo6stJc4f8xGvyuJSdEQEG484o=;
 b=jmyiiBPqcNDBInrhfsrpdJYVjPGlNMie8ZMjBEs2SYQtWCMTT8FhqUV98FNhAO7q5y
 Q12jfMg+M6GeW6iR8fwvAJl4TklmDefD/bD6TPjfHp4OGx9lp+t8+jQ9thqu6iyBrfar
 BJdQdYtGqERHqtLJm6nTz47Sjh5vEgVR+3ZOc9Ce7ylnYC+nYOmIwRsX5AyAMa2Hc5g6
 8Jrt8aY5Me8OsoMutkbAmwpw3ER2c6Y5sPSWKUKRPYwGtOM/Zf4TlSeI5XiR8oT7Phr4
 bNodQgZ8JJ4cxwnmLOqSf/dYd1KUtDvQRXKSUdrMLo0q8TdwzIPBcVdVa6Qnl86ps1BS
 quUA==
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=k9r60rztpKam0KxapGo6stJc4f8xGvyuJSdEQEG484o=;
 b=i/VurW2mRwuI+A1YuBoCbRila9F5JS/0kNEwHJbGhX6yWnL9eERQASRrvI+dpDMSgC
 pmbFoTBzrUhgVEzCo3HLsRUsuncauqi1ZRFZZOyMfeSUlKBgV7mi4BjRrK2Y/UEp8UEP
 /AhyqLPwLKTjb2MiAkefAX9LcUh2F1tC4T44TBygAFTiZJAWT9zqj+fzI6IspgJFYMRz
 vk6TUqsrmznrKG3XCSTXirwgw5SQw9BVtkaJ/ef0+4iAZMINSPZWZ4RxWRnqSl88WnQ1
 l5LlaGYSvMUO2AwqLoxLiRGClaOtv75qkWR+7Dxtnaf9VamOX+0CCjepytsB0DX9MpLC
 AITQ==
X-Gm-Message-State: ANoB5pkz4OD5YBUusI5WR4+pTZOrkNp6VVimuvConp48ECI/4rX3uoSw
 kXhQPynGTzmN2ZE/fq5PzLiI517UXTuMhlBsibg2TCFTUOY=
X-Google-Smtp-Source: AA0mqf6KaqJdWZjKIVhDIlaZ3GlufxhKtBQPPzOhTh/08Ku9bO6uPmA7uLPUDEAkWT8Auu1pJEJbslD6mm7Fx5E4mZo=
X-Received: by 2002:a05:6638:3b4:b0:38a:46d2:18a5 with SMTP id
 z20-20020a05663803b400b0038a46d218a5mr12034256jap.155.1671503715664; Mon, 19
 Dec 2022 18:35:15 -0800 (PST)
MIME-Version: 1.0
References: <CALZpt+GZy1F8S=wYbMmHYE4x21mROJy55pkbmzmSE_a6cULeiw@mail.gmail.com>
In-Reply-To: <CALZpt+GZy1F8S=wYbMmHYE4x21mROJy55pkbmzmSE_a6cULeiw@mail.gmail.com>
From: Antoine Riard <antoine.riard@gmail.com>
Date: Tue, 20 Dec 2022 02:35:04 +0000
Message-ID: <CALZpt+GhSRZD5O4gxTvt09BqXthMt4oFBdO9RG-pOSWpCraqdw@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000368a6805f03949b7"
X-Mailman-Approved-At: Tue, 20 Dec 2022 09:07:18 +0000
Subject: Re: [bitcoin-dev] Bitcoin Contracting Primitives WG 2nd Meeting,
 Tuesday 20 Dec. 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, 20 Dec 2022 02:35:19 -0000

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

Reminder: this is happening this _upcoming_ Tuesday.

Looking forward to the second session to roam over all the contracting
protocol use-cases and primitives and then listen to everyone doing
research in the contracting primitives/covenant spaces, where they would
like more brain power!

Best,
Antoine



Le lun. 12 d=C3=A9c. 2022 =C3=A0 16:13, Antoine Riard <antoine.riard@gmail.=
com> a
=C3=A9crit :

> Hi list,
>
> I'm proposing Tuesday 20th December at 18:00 UTC, i.e 1 week from now for
> the 2nd Bitcoin contracting primitives WG meeting.
>
> As a soft proposal for an agenda, the first part could be to roam over al=
l
> the contracting protocol use-cases and corresponding primitives, to ensur=
e
> there is exhaustivity of the R&D effort w.r.t known ideas issued by the
> community during the past years. If you have been working on a primitive
> and corresponding use-cases, and it's missing in the current listing, fee=
l
> free to open a PR or bump me to do so.
>
> The second part could be to take time to listen to everyone blockers in
> their contracting primitives/covenant research, if someone would like mor=
e
> review on their proposals, or if someone would like to work on a code
> implementation and it misses familiarity with Bitcoin Core Script
> interpreter, or if someone would like to experiment a minimal use-case on
> bitcoin-inquisition, or if someone has conceptual questions on the
> primitive design approach, or if someone thinking to propose a new
> cryptosystem at the consensus-level for Bitcoin, or whatever [0].
>
> Communication venue is #bitcoin-contracting-primitives-wg on Libera Chat.
> Logs of the previous session are available here [1].
>
> Let it know if you have more questions or feedback.
>
> Cheers,
> Antoine
>
> [0] My own goal is to keep rolling the ball on a taproot annex
> implementation (https://github.com/bitcoin-inquisition/bitcoin/pull/9) as
> it could be useful as a fee-bumping primitive/constrained amount
> malleability extension for multi-party channels, and potentially other us=
es.
>
> [1]
> https://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/mee=
tings/meetings-15-11.md
>

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

<div dir=3D"ltr">Reminder: this is happening this _upcoming_ Tuesday.<div><=
br></div><div>Looking forward to the second session to roam over all the co=
ntracting protocol use-cases and primitives and then listen to everyone=C2=
=A0doing research in the contracting=C2=A0primitives/covenant spaces, where=
 they would like more brain power!</div><div><br></div><div>Best,</div><div=
>Antoine</div><div><br></div><div><br></div></div><br><div class=3D"gmail_q=
uote"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0lun. 12 d=C3=A9c. 2022 =
=C3=A0=C2=A016:13, Antoine Riard &lt;<a href=3D"mailto:antoine.riard@gmail.=
com">antoine.riard@gmail.com</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-widt=
h:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr">Hi list,<br><br>I&#39;m proposing Tuesday 20th Dec=
ember at 18:00 UTC, i.e 1 week from now for the 2nd Bitcoin contracting pri=
mitives WG meeting.<br><br>As a soft proposal for an agenda, the first part=
 could be to roam over all the contracting protocol use-cases and correspon=
ding primitives, to ensure there is exhaustivity of the R&amp;D effort w.r.=
t known ideas issued by the community during the past years. If you have be=
en working on a primitive and corresponding use-cases, and it&#39;s missing=
 in the current listing, feel free to open a PR or bump me to do so.<br><br=
>The second part could be to take time to listen to everyone blockers in th=
eir contracting primitives/covenant research, if someone would like more re=
view on their proposals, or if someone would like to work on a code impleme=
ntation and it misses familiarity with Bitcoin Core Script interpreter, or =
if someone would like to experiment a minimal use-case on bitcoin-inquisiti=
on, or if someone has conceptual questions on the primitive design approach=
, or if someone thinking to propose a new cryptosystem at the consensus-lev=
el for Bitcoin, or whatever [0].<br><br>Communication venue is #bitcoin-con=
tracting-primitives-wg on Libera Chat. Logs of the previous session are ava=
ilable here [1].<br><br>Let it know if you have more questions or feedback.=
<br><br>Cheers,<br>Antoine<br><br>[0] My own goal is to keep rolling the ba=
ll on a taproot annex implementation (<a href=3D"https://github.com/bitcoin=
-inquisition/bitcoin/pull/9" target=3D"_blank">https://github.com/bitcoin-i=
nquisition/bitcoin/pull/9</a>) as it could be useful as a fee-bumping primi=
tive/constrained amount malleability extension for multi-party channels, an=
d potentially other uses.<br><br>[1] <a href=3D"https://github.com/ariard/b=
itcoin-contracting-primitives-wg/blob/main/meetings/meetings-15-11.md" targ=
et=3D"_blank">https://github.com/ariard/bitcoin-contracting-primitives-wg/b=
lob/main/meetings/meetings-15-11.md</a><br></div>
</blockquote></div>

--000000000000368a6805f03949b7--