From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 0AADCC001E for ; Mon, 10 Jan 2022 07:59:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id D83DD827F3 for ; Mon, 10 Jan 2022 07:59:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -4.197 X-Spam-Level: X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HHP7jIB_xdx0 for ; Mon, 10 Jan 2022 07:59:34 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by smtp1.osuosl.org (Postfix) with ESMTPS id C2C1D82771 for ; Mon, 10 Jan 2022 07:59:33 +0000 (UTC) Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) (authenticated bits=0) (User authenticated as jlrubin@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 20A7xUQ7031814 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 10 Jan 2022 02:59:31 -0500 Received: by mail-lf1-f42.google.com with SMTP id br17so10128446lfb.6 for ; Sun, 09 Jan 2022 23:59:31 -0800 (PST) X-Gm-Message-State: AOAM533dsVWV3aGG6fopAdKckmyRJv4/jU2zoSkra/Ab0UwJRfkl8RIU BKhp8TYC9LRoYlRVdVYxwgrmwBO/Wk7DJncfX9k= X-Google-Smtp-Source: ABdhPJwSlvMc0JP9iOMe05goOsQ8B4gubBAWaq/ef8P/DEYuyx8/Q43/BPMHp2EGsntylYV3uODinqeTHgnpQtUUS4k= X-Received: by 2002:a05:651c:160a:: with SMTP id f10mr35925378ljq.212.1641801570018; Sun, 09 Jan 2022 23:59:30 -0800 (PST) MIME-Version: 1.0 From: Jeremy Date: Sun, 9 Jan 2022 23:59:18 -0800 X-Gmail-Original-Message-ID: Message-ID: To: Bitcoin development mailing list Content-Type: multipart/alternative; boundary="0000000000005f6a1505d535b71e" Subject: [bitcoin-dev] BIP-119 Meeting Reminder and Prelim Agenda 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, 10 Jan 2022 07:59:38 -0000 --0000000000005f6a1505d535b71e Content-Type: text/plain; charset="UTF-8" Hi all, As a reminder the first meeting for CTV will be this Tuesday at 12:00PM PT. Based on feedback, I have included a preliminary agenda and time allocation for the meeting at the end of this email. The main part of the meeting will run for 1.5 hours, and will be followed by a post meeting discussion of length 30 minutes for discussing broader next steps and consensus seeking processes (this is separate to break up the technical review from the metaphysics of consensus discussion and allow those who do not wish to discuss a polite exit). The agenda does not thoroughly cover motivations or use cases for CTV, such as congestion control, vaults, payment pools, or non-interactive contract openings. Those can be found in a multitude of sources (such as https://rubin.io/advent21, https://learn.sapio-lang.org, https://utxos.org, or https://github.com/kanzure/python-vaults/tree/master/vaults). Specific applications built on CTV will be best reviewed in follow up meetings as technical evaluation of how well CTV works for use cases requires a deep understanding of how the CTV primitive works. For similar reasons, this agenda does not do a deep dive into alternatives to CTV. That discussion can be best had following a thorough review of CTV itself. Helpful links for depthening understanding on covenant properties, proposals, and varieties included below in a (loosely) recommended reading order: https://rubin.io/bitcoin/2021/12/04/advent-7/ https://rubin.io/bitcoin/2021/12/05/advent-8/ https://rubin.io/blog/2021/07/02/covenants/ https://utxos.org/alternatives/ https://arxiv.org/abs/2006.16714 https://rubin.io/bitcoin/2021/12/24/advent-27/ https://github.com/bitcoin/bips/blob/master/bip-0119.mediawiki#feature-redundancy https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-September/019424.html If you feel particular topics important to you are not represented in this agenda or if I can make any improvements otherwise, please drop me a note and I will endeavor to ensure they are either slotted into this meeting or included in a second meeting. That the meeting is tightly scheduled is by design: I want to respect everyone's time and ensure that the meeting is highly productive. There is always room for follow ups or further exploration at future meetings or as mailing list follow ups. Looking forward to discussing with you on tuesday, Jeremy *#topic Overview of BIP & Q&A (40 Mins)* #subtopic what does CTV do? (5 minutes) #subtopic which fields are in the digest? (5 minutes) #subtopic the order / structure of fields in the digest? (5 minutes) #subtopic the half-spend problem/solution? (5 minutes) #subtopic using a NOP v.s. successX / legacy script types? (5 minutes) #subtopic using sha256 v.s. Ripemd160 (5 minutes) #subtopic general q&a (10 minutes) *#topic Overview of Implementation & Testing (30 Minutes)* #subtopic implementation walkthrough (15 minutes) #subsubtopic validation burdens & caching (5 minutes) #subtopic vectors: tx_valid.json + tx_invalid.json + transaction hashes checking (2 minutes) #subtopic functional test walkthrough (8 minutes) *#topic Proposed Timeline Technical Feasibility (not advisibility) (10 minutes)* *#topic Feedback on how to Structure Bounty Program (10 minutes)* #post-meeting *#topic open-ended feedback (is this meeting helpful, what could be better, etc) (10 minutes)#topic What's required to get consensus / next steps? (20 minutes)* #subtopic Discussion of "soft signals" utxos.org/signals (10 minutes) #subtopic Discussion of activation mechanisms (10 minutes) -- @JeremyRubin --0000000000005f6a1505d535b71e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

As a reminder the first meeting for CTV wil= l be this Tuesday at 12:00PM PT.

Based on feedback, I have included=C2=A0a preliminary= agenda and time allocation for the meeting at the end of this email. The main part of the meeting will ru= n for 1.5 hours, and will be followed by a post meeting discussion of lengt= h 30 minutes for discussing broader next steps and consensus seeking proces= ses (this is separate to break up the technical review from the metaphysics= of consensus discussion and allow those who do not wish to discuss a polit= e exit).

The agenda does not th= oroughly cover motivations or use cases for CTV, such as congestion control, vaults, payment pools,= or non-interactive contract openings. Those can be found in a multitude of= sources (such as https://rubin.io/ad= vent21, https://learn.sapio-la= ng.org, https://utxos.org, or https://github.com/kanzure/python-vaults/= tree/master/vaults). Specific applications built on CTV will be best re= viewed in follow up meetings as technical evaluation of how well CTV works = for use cases requires a deep understanding of how the CTV primitive works.

For similar reasons, this agenda does not do a deep dive into altern= atives to CTV. That discussion can be best had following a thorough review = of CTV itself. Helpful links for depthening understanding on covenant prope= rties, proposals, and varieties included below in a (loosely) recommended r= eading order:
https://arxiv.org/abs= /2006.16714
https://rubin.io/bitcoin/2021/12/24/advent-27/


If you feel particular topics important to you are not represented in= this agenda or if I can make any improvements otherwise, please drop me a = note and I will endeavor to ensure they are either slotted into this meetin= g or included in a second meeting.

That the meeting is tightly= scheduled is by design: I want to respect everyone's time and ensure t= hat the meeting is highly productive. There is always room for follow ups o= r further exploration at future meetings or as mailing list follow ups.
Looking forward to dis= cussing with you on tuesday,

<= /div>
Jeremy


#topic Overview of BIP & Q&A (40 Mins)

#subtopic wha= t does CTV do? (5 minutes)

#subtopic which fields are in the digest?= (5 minutes)

#subtopic the order / structure of fields in the digest= ? (5 minutes)

#subtopic the half-spend problem/solution? (5 minutes)=

#subtopic using a NOP v.s. successX / legacy script types? (5 minut= es)

#subtopic using sha256 v.s. Ripemd160 (5 minutes)

#subtop= ic general q&a (10 minutes)=

#topic Overview of Implementation & Testing (30 Minutes)
=
#subtopic implementation walkthrough (15 minutes)

#subsubtop= ic validation burdens & caching (5 minutes)

#subtopic vectors: t= x_valid.json + tx_invalid.json + transaction hashes checking (2 minutes)
#subtopic functional test walkthrough (8 minutes)

#topic Pro= posed Timeline Technical Feasib= ility (not advisibility) (10 minutes)

<= b>#topic Feedback on how to Structure Bounty Program (10 minutes)
#post-meeting

#topic=C2=A0open-ended feedback (is this meeting helpful, what could be better, etc)=C2=A0(10 minutes)
#= topic What's required to get consensus / next steps? (20 minutes)
#subtopic Discussion of "= ;soft signals" utxos.org/signals<= /a> (10 minutes)
#subtopic Discussion of activation mechanisms (10 minut= es)



 --0000000000005f6a1505d535b71e--