From: Antoine Riard <antoine.riard@gmail•com>
To: alicexbt <alicexbt@protonmail•com>
Cc: 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: Tue, 15 Nov 2022 18:49:17 -0500 [thread overview]
Message-ID: <CALZpt+EgifiVe9UrktBxAuOm9QHYTLs+uv+nsJN-9pBbk0jsJw@mail.gmail.com> (raw)
In-Reply-To: <KC6W2mW10GBn00XMNUJDUxp27BAOM94o1PE_CVpnMjKVLwPwLMiBQHCfNDZZqR619BMZJyq3hskVhK5T24Kr_v4MStTL4kx74z55qRU0bVY=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 3216 bytes --]
Hi alicexbt,
CTV is listed here:
https://github.com/ariard/bitcoin-contracting-primitives-wg/tree/main/primitives
as one of the primitive subject of research. Contributions are welcome.
Best,
Antoine
Le mar. 15 nov. 2022 à 17:37, alicexbt <alicexbt@protonmail•com> a écrit :
> Hi Bitcoin Developers,
>
> 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!
>
>
> Wanted to add CTV: BIP-119 OP_CHECKTEMPLATEVERIFY if OP missed it.
> Easiest and best possible way to get covenants aka tx introspection with
> lot of research and development.
>
> /dev/fd0
>
> Sent with Proton Mail <https://proton.me/> secure email.
>
> ------- Original Message -------
> On Monday, November 14th, 2022 at 7:51 AM, Antoine Riard via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> 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: 5202 bytes --]
next prev parent reply other threads:[~2022-11-15 23:49 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
2022-11-15 22:36 ` alicexbt
2022-11-15 23:49 ` Antoine Riard [this message]
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+EgifiVe9UrktBxAuOm9QHYTLs+uv+nsJN-9pBbk0jsJw@mail.gmail.com \
--to=antoine.riard@gmail$(echo .)com \
--cc=alicexbt@protonmail$(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