From: Antoine Riard <antoine.riard@gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Contracting Primitives WG 3rd Meeting, Tuesday 17 Jan. 18:00 UTC
Date: Tue, 17 Jan 2023 01:50:05 +0000 [thread overview]
Message-ID: <CALZpt+GLUAqJv2GUqGLyziQ7BZgdifxvV-8fbzxqAR9Usx8LYg@mail.gmail.com> (raw)
In-Reply-To: <CALZpt+Eou=m9LnZfZoxfZcQLs7UL5Te53whNgYO1fro05iSvDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
Reminder: this is happening this _upcoming_ Tuesday.
Looking forward to the third session to roam over all the contracting
protocol use-cases and then listen to everyone doing research in the
contracting primitives/covenant spaces, where they would like more brain
power!
Best,
Antoine
Le ven. 6 janv. 2023 à 00:26, Antoine Riard <antoine.riard@gmail.com> a
écrit :
> Hi list,
>
> I'm proposing Tuesday 17th January at 18:00 UTC, i.e week from now for the
> 3rd Bitcoin contracting primitives WG meeting (the third Tuesday of January
> month, as done previously).
>
> As a soft proposal for an agenda, it would be to start with the leftover
> of the last meeting agenda. Namely, roaming over all the contracting
> protocol and use-case, 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 use-case, and it's missing in the current listing,
> feel free to open a PR or bump me to do so (still same with primitives
> themselves ofc).
>
> The second part could be to take time to listen to everyone blockers in
> their contracting primitives/covenant research.
>
> About the R&D effort, one of my personal goal for the coming year would be
> to nurture some websites, with the archive material progressively gathered
> in the repository. The website would present the contracting protocol
> research according to the best engineering/scientific
> standards and ensure ideas neutrality. Ideally, it would enable collection
> of feedback on dimensions like privacy or economic scaling from the Bitcoin
> community of stakeholders at large, with Pretty Graphics (tm).
>
> Beyond, pursuing a "decentralized" spirit, looking forward to starting
> rotating meetings host during the year, as we're doing with BOLTs where
> it's rotating between Lightning implementations contributors. If you're
> interested in hosting one of the monthly meetings, feel free to open an
> issue against the repository or bump me.
>
> Communication venue is #bitcoin-contracting-primitives-wg on Libera Chat.
> Logs of the previous session are available here [0].
>
> Let it know if you have more questions or feedback.
>
> Cheers,
> Antoine
>
> [0]
> https://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/meetings/meetings-20-12.md
>
[-- Attachment #2: Type: text/html, Size: 2888 bytes --]
prev parent reply other threads:[~2023-01-17 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 0:26 [bitcoin-dev] Bitcoin Contracting Primitives WG 3rd Meeting, Tuesday 17 Jan. 18:00 UTC Antoine Riard
2023-01-17 1:50 ` 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+GLUAqJv2GUqGLyziQ7BZgdifxvV-8fbzxqAR9Usx8LYg@mail.gmail.com \
--to=antoine.riard@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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