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"
Subject: Re: [bitcoin-dev] Bitcoin Contracting Primitives WG 2nd Meeting,
 Tuesday 20 Dec. 18:00 UTC
Precedence: list

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