Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id B3FDAC002D for ; Tue, 15 Nov 2022 23:49:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 800EF4090D for ; Tue, 15 Nov 2022 23:49:31 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 800EF4090D Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=WvThTmd3 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZzAs-XiIEajV for ; Tue, 15 Nov 2022 23:49:30 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org CA90E402B3 Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) by smtp4.osuosl.org (Postfix) with ESMTPS id CA90E402B3 for ; Tue, 15 Nov 2022 23:49:29 +0000 (UTC) Received: by mail-io1-xd2a.google.com with SMTP id h206so12005215iof.10 for ; Tue, 15 Nov 2022 15:49:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=unv/FKGLbc33NUSYaEqC0gdK6MwfcnlV7bWi2cWsBp4=; b=WvThTmd3Oyz8rNmv0GSFJsQd9WHPER5ttLThkRqE/geJbtzs9mwKTxc8Y07BBqSQja qAWQUAHmWLpYK1lvTUK4TE/MjqfjZPrw3Km1x8iWwdd00A0Y87VdcenfhJHUgLhc/abR ao+boK1YipQlbKrCSaCGGMvAltmhfdMt2SxVwTL0/NVpHArjO4ruyszpypAN7So1C0dw uN32omS+7+N/M4IJ3wRYzOZ0aOOH2mNMYvC/sBQe4i3zXm96Fg7frExNdnM2ZhkPE0AZ e5ltNeHvyGt4w7SCE2j+GXdHJQkJ9IAEAWpMs1GJ36oy+VTMT/e/bTGUo0+X77rFNK0V qpzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=unv/FKGLbc33NUSYaEqC0gdK6MwfcnlV7bWi2cWsBp4=; b=JOyPP2gELiyNqlZrhN3NRxYhZ5V3meJQeXRVLzZs+CHdlAG+jmGLnbNtTAipubd89b PkqGItRwrHaaMpZmVcp9yHCzD1wYN62LSpQ/KJBWoFGsq6BWuGEIfbfXbCj2yugZgFIb 5UcZJ2JAIRzYWmVY6IzkXHDz1I17CnyspZbdbDWS8EJlyr3DFbN5jsy2RvfKyeQoQ91J 9a1149DpmR1O6B3ios0C04FCgAuB7Fsjntrw9JEIjwUY3ICGlXjllby/AAO0o/aEZl1F k8yWfdZL3C27VSFMV8M1lt11gc7lkt17CofUOixJG84zR7ahWhAizCTuxDjqF7Lv0hD2 9mBw== X-Gm-Message-State: ANoB5pkqcowpbOopHUahrDTwcMpBW5A6Z+JoRFzoYxfTC4Ay7HPMVowi D1W8h24gpNK/ScJrj/g1ekL8Ih1R+3UVV35V2fk= X-Google-Smtp-Source: AA0mqf7/XJcZXrvZ4ZcGheQTe452YAHRenzEZ5ejfyYrv8uUUOry9hj5gMK2zcjZUZQwm5r3CcTeLaEI99SjdeVC25U= X-Received: by 2002:a02:a04c:0:b0:363:b3c4:5c47 with SMTP id f12-20020a02a04c000000b00363b3c45c47mr9431350jah.237.1668556168840; Tue, 15 Nov 2022 15:49:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Antoine Riard Date: Tue, 15 Nov 2022 18:49:17 -0500 Message-ID: To: alicexbt Content-Type: multipart/alternative; boundary="000000000000bb48db05ed8b010a" X-Mailman-Approved-At: Wed, 16 Nov 2022 00:28:09 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Bitcoin Contracting Primitives WG 1st Meeting, Tuesday 15 Nov. 18:00 UTC X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2022 23:49:31 -0000 --000000000000bb48db05ed8b010a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi alicexbt, CTV is listed here: https://github.com/ariard/bitcoin-contracting-primitives-wg/tree/main/primi= tives as one of the primitive subject of research. Contributions are welcome. Best, Antoine Le mar. 15 nov. 2022 =C3=A0 17:37, alicexbt a =C3= =A9crit : > 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, Z= K > 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 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, Z= K > rollups, new contracting protocols and many more ideas! > > Best, > Antoine > > Le lun. 31 oct. 2022 =C3=A0 20:47, Antoine Riard a > =C3=A9crit : > >> 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 i= n >> the Bitcoin space, let it know. We can talk about a better schedule duri= ng >> 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 happen= ing >> 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 ther= e: >> 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. >> > > --000000000000bb48db05ed8b010a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi alicexbt,

CTV is listed her= e: https://github.com/ariard/bitcoin-contracting-primitiv= es-wg/tree/main/primitives as one of the primitive subject of research.= Contributions are welcome.

Best,
Antoine
Le=C2=A0= mar. 15 nov. 2022 =C3=A0=C2=A017:37, alicexbt <alicexbt@protonmail.com> a =C3=A9crit=C2=A0:
Hi Bitcoin Developers,

Looking = forward to the first session, listening to everyone's thoughts about wh= at 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:=C2=A0BIP-119= OP_CHECKTEMPLATEVERIFY if OP missed it. Easiest and best possible way to g= et covenants aka tx introspection with lot of research and development.

<= /div>
/dev/fd0<= /div>
=20
=20
Sent with Proton Mail secure email.

------- Original Message -------
On Monday, November 14th, 2022 at 7:51 AM, Antoine Riard via bitcoi= n-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:

Reminder: this is happening thi= s _upcoming_ Tuesday.

Looking forward to the first session, l= istening to everyone's thoughts about what could be the scope discussed= by this new community process: anyprevout, recursive covenants, introspect= ion, new malleability flags, ZK rollups, new contracting protocols and many= more ideas!

Best,
Antoine

Le lun. 31 oct. 2022= =C3=A0 20:47, Antoine Riard <antoine.riard@gmail= .com> a =C3=A9crit :
Hi list,

After I have been asked o= ffline the exact date when those meetings were actually starting, I'm p= roposing 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/l= ighnting specs meetings/core dev meetings in the past, weekly sounds too mu= ch, 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-pri= mitives-wg on Libera Chat [1]. Feel free to lurk already and ask questions.=

No consistent agenda beyond listening to every attendee their expec= tations, ideas, subjects of interests they would like to see happening with= this new covenants/contracting primitives R&D process.

If you h= ave been working on a contracting protocols/side-chains/rollups/other use-c= ases that could benefit from extended Bitcoin contracting primitives, feel = free to open an issue there: https://github.com/ariard/bitcoin-contracting-primitives-wg/is= sues

Let it know if you have more questions or feedback.

= Cheers,
Antoine

[0] It would be great to have a schedule inclusiv= e of most timezones we can, 18:00 UTC might be too early for Asian and Ocea= nic ones. Later, we start to be exclusive towards contributors in Eastern E= urope.

[1] There have been more voices suggesting jitsi/audio-based = meetings rather than IRC. It's a cool format too, though coming with tr= ade-offs.

--000000000000bb48db05ed8b010a--