From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id D23E9C0001 for ; Sun, 21 Feb 2021 10:10:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by fraxinus.osuosl.org (Postfix) with ESMTP id BD42B85CFF for ; Sun, 21 Feb 2021 10:10:10 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from fraxinus.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VpgtjRLKpm0U for ; Sun, 21 Feb 2021 10:10:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162]) by fraxinus.osuosl.org (Postfix) with ESMTPS id 97EBB8553B for ; Sun, 21 Feb 2021 10:10:09 +0000 (UTC) Received: from w3.tutanota.de (unknown [192.168.1.164]) by w1.tutanota.de (Postfix) with ESMTP id 090D5FBF64E for ; Sun, 21 Feb 2021 10:10:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1613902208; s=s1; d=tutanota.de; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender; bh=Bm1p6wWr2o8gXsTOcTcjlUWbj24L9V4hpjYaVnLD+tM=; b=kf/1SD7zlkqwWYfYPKQTu6kJjtRCiaJNTIBwa/BdZv/pAo+5kXvM7IOriOJxg06u WoW0NeegnVfafHB1hPdRZisfRkko+JM2QqQKhGdGWjOnPeWDXUvjaGOOlm4TZtYjXpd QznfmoMm34oSErHq1wfciO6XeA30kuaLbuO3nk9z21T+2n+al3HbheYTs/orQHvhXWq tAhTAxW9ggTrJqLBPfgWXum9NpU6ta1W32ZEON7Pujkmay+zr+YTht7CSZd+0WN1ATM 4xiRchfS272HNQ676DUa480uEJLsLTV3V8ZnY/ZB1G0uNouecYu9ICUVlwxLGJlZVFv bKF84bTXbg== Date: Sun, 21 Feb 2021 11:10:08 +0100 (CET) From: Prayank To: Bitcoin Dev Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_433038_1217980207.1613902208027" X-Mailman-Approved-At: Mon, 22 Feb 2021 08:02:33 +0000 Subject: Re: [bitcoin-dev] Yesterday's Taproot activation meeting on lockinontimeout (LOT) 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: Sun, 21 Feb 2021 10:10:10 -0000 ------=_Part_433038_1217980207.1613902208027 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Everyone, The below comment by Matt about different implementations and their opinion= on `lockinontimeout` is from 18 Feb 2021 communication:=C2=A0https://lists= .linuxfoundation.org/pipermail/bitcoin-dev/2021-February/018433.html >=C2=A0If the eventual outcome is that different implementations (that have= material *transaction processing* userbases, and I=E2=80=99m not sure to w= hat extent that=E2=80=99s true with Knots) ship different consensus rules, = we should stop here and not activate Taproot. Seriously. Bitcoin is a conse= nsus system. The absolute worst outcome at all possible is to have it fall = out of consensus. I don't agree to the part that 'we should stop and not activate taproot'. I= nstead it will be helpful if we can educate most of the people about trade-= offs involved in both options with some tables, charts etc. I think its time to use Bitcoin Knots for more projects and also maintain m= ultiple forks of Bitcoin Core. This is not just limited to `LOT=3DTrue or F= alse` but few other things and in general its good for decentralization of = Bitcoin. Bitcoin Core is used by most of the nodes according to this pie ch= art:=C2=A0https://luke.dashjr.org/programs/bitcoin/files/charts/software.ht= ml=C2=A0however having multiple forks of Bitcoin Core with real usage, more= maintainers in different parts of the world (some even anon), few differen= t features, more reviewers, better communication channels etc. will help ev= eryone involved in Bitcoin. I am working on a project right now which involves multisig, discreet log c= ontracts, liquid etc. Using bitcoin-s for it because I need DLC but still d= epending on Bitcoin Core in it. Would try Bitcoin Knots and other implement= ations soon and also have been looking for developers good with C++ and Pyt= hon, living in India who are interested to maintain a fork of Bitcoin Core = with few changes. I had shared about in replies to Amir Taaki's tweet few d= ays back. -- Prayank ------=_Part_433038_1217980207.1613902208027 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Everyone,

The below comment by M= att about different implementations and their opinion on `lockinontimeout` = is from 18 Feb 2021 communication: h= ttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-February/018433= .html

> If the eventual outcome = is that different implementations (that have material *transaction processi= ng* userbases, and I=E2=80=99m not sure to what extent that=E2=80=99s true = with Knots) ship different consensus rules, we should stop here and not act= ivate Taproot. Seriously. Bitcoin is a consensus system. The absolute worst= outcome at all possible is to have it fall out of consensus.
I don't agree to the part that 'we should stop and not ac= tivate taproot'. Instead it will be helpful if we can educate most of the p= eople about trade-offs involved in both options with some tables, charts et= c.

I think its time to use Bitcoin Knots for= more projects and also maintain multiple forks of Bitcoin Core. This is no= t just limited to `LOT=3DTrue or False` but few other things and in general= its good for decentralization of Bitcoin. Bitcoin Core is used by most of = the nodes according to this pie chart: https://luk= e.dashjr.org/programs/bitcoin/files/charts/software.html however h= aving multiple forks of Bitcoin Core with real usage, more maintainers in d= ifferent parts of the world (some even anon), few different features, more = reviewers, better communication channels etc. will help everyone involved i= n Bitcoin.

I am working on a project right n= ow which involves multisig, discreet log contracts, liquid etc. Using bitco= in-s for it because I need DLC but still depending on Bitcoin Core in it. W= ould try Bitcoin Knots and other implementations soon and also have been lo= oking for developers good with C++ and Python, living in India who are inte= rested to maintain a fork of Bitcoin Core with few changes. I had shared ab= out in replies to Amir Taaki's tweet few days back.

--
Prayank

------=_Part_433038_1217980207.1613902208027--