public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Antoine Riard <antoine.riard@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Contracting Primitives WG 2nd Meeting, Tuesday 20 Dec. 18:00 UTC
Date: Tue, 20 Dec 2022 02:35:04 +0000	[thread overview]
Message-ID: <CALZpt+GhSRZD5O4gxTvt09BqXthMt4oFBdO9RG-pOSWpCraqdw@mail.gmail.com> (raw)
In-Reply-To: <CALZpt+GZy1F8S=wYbMmHYE4x21mROJy55pkbmzmSE_a6cULeiw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]

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éc. 2022 à 16:13, Antoine Riard <antoine.riard@gmail•com> a
écrit :

> 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 all
> the contracting protocol use-cases and corresponding primitives, to ensure
> 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, feel
> 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 more
> 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 uses.
>
> [1]
> https://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/meetings/meetings-15-11.md
>

[-- Attachment #2: Type: text/html, Size: 2790 bytes --]

      reply	other threads:[~2022-12-20  2:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 16:13 Antoine Riard
2022-12-20  2:35 ` Antoine Riard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALZpt+GhSRZD5O4gxTvt09BqXthMt4oFBdO9RG-pOSWpCraqdw@mail.gmail.com \
    --to=antoine.riard@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox