From: Antoine Riard <antoine.riard@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Contracting Primitives WG 1st Meeting, Tuesday 15 Nov. 18:00 UTC
Date: Sun, 13 Nov 2022 21:21:16 -0500 [thread overview]
Message-ID: <CALZpt+E0PSc_DD39E1-3hGYvpw3ok91Nc5DLTTh9FPdOKF_TYg@mail.gmail.com> (raw)
In-Reply-To: <CALZpt+EygPsez0c84Yfmc6h+L7Ji8C3zE_E=EzPzLh4XWNHvZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]
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 à 20:47, Antoine Riard <antoine.riard@gmail•com> a
écrit :
> 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 during
> 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 happening
> 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.
>
[-- Attachment #2: Type: text/html, Size: 2542 bytes --]
next prev parent reply other threads:[~2022-11-14 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 0:47 Antoine Riard
2022-11-14 2:21 ` Antoine Riard [this message]
2022-11-15 22:36 ` alicexbt
2022-11-15 23:49 ` Antoine Riard
2022-11-15 23:47 ` Antoine Riard
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+E0PSc_DD39E1-3hGYvpw3ok91Nc5DLTTh9FPdOKF_TYg@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