Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id BEE05C002D for ; Mon, 12 Dec 2022 16:13:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id A579C40260 for ; Mon, 12 Dec 2022 16:13:20 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org A579C40260 Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=fYzvLBGg 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 smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPQBZaMMUQ91 for ; Mon, 12 Dec 2022 16:13:19 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org A982B40256 Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) by smtp2.osuosl.org (Postfix) with ESMTPS id A982B40256 for ; Mon, 12 Dec 2022 16:13:19 +0000 (UTC) Received: by mail-io1-xd31.google.com with SMTP id g20so163232iob.2 for ; Mon, 12 Dec 2022 08:13:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=nz8Q0BlrPJjxr24Va7/vtLqoUAiWDeZQep1IY/p9z40=; b=fYzvLBGgBsR21+kYMj4m3+w30zdvw98podMPzkeZ0CeMWyWMexHB9ibj776AfnYATg sbCK94/agfSEcIUTd9eUC5e/m71ek4kXBmaH4pwMDZjSEd5j/QH84kAf+sHvbWc+ue2o ZQ1SgCvT+uCmhQLLW0TE0056gOfMf9AtJxjDEmKUBsu3BQepbt8vFLn+JOzL3D2DZwkg pVBBzfjM6oUkOw99C4dtbBXlxpBKI06ocIcRKhwwxVzn5sRk6d4nhfNINx5Uh6yYUkI8 ZphIkxRprc/iIgnwy/ropYgyYvrW6+cUCk/VwzUUsdCpBHwE5hibjS96E4wQUDTDZsmf wpSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=nz8Q0BlrPJjxr24Va7/vtLqoUAiWDeZQep1IY/p9z40=; b=AB9zTfoagTJ8UR+H1ptm1V+pW2DPc0vI1YR3x/w6DSthSskZZDW//pYBqMVxP1S3Ru CWjT+xJr1ONRDYA17zVeJY0BmTrNrR9vLJCEaNkAwlTWs0EGaN4T53pUdqg0NxQFsiNp X6heIQ6DQ9tLOsnO8VwT53fsTD3q9FphTt+VMLaGZfnuEpew7jMK0KuTwqDFs/IaUE4L pNZ7bWjZ5+lqxWlvywq+XKe4m4PGYWUMNTpo6dFbhzvzValh4+0u3JH4541EDoOzCklm 7pH+6He/N4yXZn0niM6d6yMNmx/WWLiUFiO7WCbP43WFgEfqbvZiS0fAG5Pyp+6ds97o 3cIA== X-Gm-Message-State: ANoB5pkNTIQXtM3VtUHzSKg/U7c4ULjtNX/Z6P7zWcoYtV0trTRMYAnS W6OmbmLpqqln8iN7oQQc287Dmc7GnMkWY9iPDFrHZSI5pTivrw== X-Google-Smtp-Source: AA0mqf7B4FA7nWSuXTmekG5KvyFRw2Pk1SFnvfmtrvnu2RjvtYgz55Q2p5HqINDIeLGzrjgSUqdNng2faeWVdv8cXGA= X-Received: by 2002:a02:914b:0:b0:363:b3c4:5c47 with SMTP id b11-20020a02914b000000b00363b3c45c47mr38112595jag.237.1670861598455; Mon, 12 Dec 2022 08:13:18 -0800 (PST) MIME-Version: 1.0 From: Antoine Riard Date: Mon, 12 Dec 2022 11:13:07 -0500 Message-ID: To: Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000000b862005efa3c846" X-Mailman-Approved-At: Mon, 12 Dec 2022 17:46:55 +0000 Subject: [bitcoin-dev] Bitcoin Contracting Primitives WG 2nd Meeting, Tuesday 20 Dec. 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: Mon, 12 Dec 2022 16:13:20 -0000 --0000000000000b862005efa3c846 Content-Type: text/plain; charset="UTF-8" Hi list, I'm proposing Tuesday 20th December at 18:00 UTC, i.e 1 week from now for the 2nd Bitcoin contracting primitives WG meeting. As a soft proposal for an agenda, the first part could be to roam over all the contracting protocol use-cases and corresponding primitives, 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 primitive and corresponding use-cases, and it's missing in the current listing, feel free to open a PR or bump me to do so. The second part could be to take time to listen to everyone blockers in their contracting primitives/covenant research, if someone would like more review on their proposals, or if someone would like to work on a code implementation and it misses familiarity with Bitcoin Core Script interpreter, or if someone would like to experiment a minimal use-case on bitcoin-inquisition, or if someone has conceptual questions on the primitive design approach, or if someone thinking to propose a new cryptosystem at the consensus-level for Bitcoin, or whatever [0]. Communication venue is #bitcoin-contracting-primitives-wg on Libera Chat. Logs of the previous session are available here [1]. Let it know if you have more questions or feedback. Cheers, Antoine [0] My own goal is to keep rolling the ball on a taproot annex implementation (https://github.com/bitcoin-inquisition/bitcoin/pull/9) as it could be useful as a fee-bumping primitive/constrained amount malleability extension for multi-party channels, and potentially other uses. [1] https://github.com/ariard/bitcoin-contracting-primitives-wg/blob/main/meetings/meetings-15-11.md --0000000000000b862005efa3c846 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi list,

I'm proposing Tuesday 20th December at= 18:00 UTC, i.e 1 week from now for the 2nd Bitcoin contracting primitives = WG meeting.

As a soft proposal for an agenda, the first part could b= e to roam over all the contracting protocol use-cases and corresponding pri= mitives, 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 worki= ng on a primitive and corresponding use-cases, and it's missing in the = current listing, feel free to open a PR or bump me to do so.

The sec= ond part could be to take time to listen to everyone blockers in their cont= racting primitives/covenant research, if someone would like more review on = their proposals, or if someone would like to work on a code implementation = and it misses familiarity with Bitcoin Core Script interpreter, or if someo= ne would like to experiment a minimal use-case on bitcoin-inquisition, or i= f someone has conceptual questions on the primitive design approach, or if = someone thinking to propose a new cryptosystem at the consensus-level for B= itcoin, or whatever [0].

Communication venue is #bitcoin-contracting= -primitives-wg on Libera Chat. Logs of the previous session are available h= ere [1].

Let it know if you have more questions or feedback.

= Cheers,
Antoine

[0] My own goal is to keep rolling the ball on a = taproot annex implementation (https://github.com/bitcoin-inquisition/bitcoin/pull/9<= /a>) as it could be useful as a fee-bumping primitive/constrained amount ma= lleability extension for multi-party channels, and potentially other uses.<= br>
[1]
https://github.com/ariard/bitc= oin-contracting-primitives-wg/blob/main/meetings/meetings-15-11.md
<= /div> --0000000000000b862005efa3c846--