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
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Reply via email to