From: Antoine Riard <antoine.riard@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Contracting Primitives WG 4rd Meeting, Tuesday 21 Feb. 18:00 UTC
Date: Tue, 21 Feb 2023 00:40:48 +0000 [thread overview]
Message-ID: <CALZpt+HW85LiwAOQOAYCVpogr+--eT1sbt9_zK3XnT7NjuybPQ@mail.gmail.com> (raw)
In-Reply-To: <CALZpt+Ep+pSkO58eOrzM57EZCGi--iperhyiEtrGP83rLp5atA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2839 bytes --]
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évr. 2023 à 01:59, Antoine Riard <antoine.riard@gmail•com> a
écrit :
> 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
> 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 few
> 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 contracting
> primitives R&D to a large set of people beyond the usual crowd contributing
> 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/003788.html
> [1] In term of janitorial role decentralization, I think it would be
> valuable to have the event organization carried on by someone else reliable
> 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/meetings/meetings-17-01.md
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3908 bytes --]
prev parent reply other threads:[~2023-02-21 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 1:59 Antoine Riard
2023-02-21 0:40 ` 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+HW85LiwAOQOAYCVpogr+--eT1sbt9_zK3XnT7NjuybPQ@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