Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 31C3BC0001 for ; Thu, 4 Mar 2021 03:15:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 17DD14017F for ; Thu, 4 Mar 2021 03:15:47 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 0.8 X-Spam-Level: X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 8OvX42Ziu3wj for ; Thu, 4 Mar 2021 03:15:46 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) by smtp2.osuosl.org (Postfix) with ESMTPS id 10D2A42F3A for ; Thu, 4 Mar 2021 03:15:45 +0000 (UTC) Received: by mail-lf1-x133.google.com with SMTP id u4so40744034lfs.0 for ; Wed, 03 Mar 2021 19:15:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=U8KEzb0hg8WN0VtxxV0DOCh23DFR+vkrXoy+fW1VszU=; b=cV3cb49+jW3KU/RyofrUKEXLNpZ60dEWWKY7CAIkGyhEmjSy75zTIF7mMK0Ib0rYer GVUn+FnMWU988GBOk+PhwDZ9/8BCPM2W35hwy0QDK1IQ9g7cXSEgYnomDFSf1kHjbHN9 kJBrz5KThrTIejFWlDEmq9ItKsgyaa/6TEaZE3eDYV63XtR161/PKxpTP7jwPeV1IAKs L2o+iwLPvKNhCS6Gcc3kz4GJLMi9eC6NwlAmklECaieOabEMN9/ArIWwCGV/vYUFGJ15 yO+J5FnYmVjR66BT7yaFIsbJZC4GbX71AFmPK+mihL2virwaX0fosMYztOEDubwSWvxW kpWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=U8KEzb0hg8WN0VtxxV0DOCh23DFR+vkrXoy+fW1VszU=; b=Dmk/RABZO+ZOzJnF416FUZ3BQ6Ioq3Ulc+uGIm+7OdjgR6EhkEtcm6oejaZx4dznad akd4GjSTWJ7gAmrh7r5Ts+ulpolF6jCiDho4xWmkV2IwpwStewU7B4OTr+mKj/kWN6di gSx/GZFkiFt8MTb50eqUUhsWbPFQTjiolmd/f5ieDi7NYsts2bqHnYuxLN20Z7aB/IZ4 0E/bd95VO8QrpL9r0k+L0kpcdRVHLnN0hXX05QWsgebRS7yIZfPDlPTU9uucLB5v4Lix r4AEx1Wg6XRShkRXP6iL2N3DJj3buj1XziLTg/I5p8idan/XqwlnGPkwi9BI6fhdY1DH zPpQ== X-Gm-Message-State: AOAM532CXnXoNBdn8LiBO3ZMCJmvHa70uXbe8FK/z/enmiSPmwzNc94G eH+QzXjY1SAD2kKEO4cPvLRoSi8O563vOWMaSKUQkCOP X-Google-Smtp-Source: ABdhPJxatldisV4W0OZIKKfaa4zRCDZltO+ow44Y6amGm9RoBqtbj4bLPU9YxXsSYFD+fVjea9/HeKfm0TmAw7qIwAE= X-Received: by 2002:ac2:5e6a:: with SMTP id a10mr940495lfr.181.1614824310975; Wed, 03 Mar 2021 18:18:30 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ariel Luaces Date: Wed, 3 Mar 2021 18:18:29 -0800 Message-ID: To: Michael Folkson , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 04 Mar 2021 07:58:11 +0000 Subject: Re: [bitcoin-dev] =?utf-8?b?WWVzdGVyZGF54oCZcyBVQVNGIChMT1Q9dHJ1ZSkg?= =?utf-8?q?kick_off_meeting?= 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: Thu, 04 Mar 2021 03:15:47 -0000 On Wed, Mar 3, 2021 at 12:25 PM Michael Folkson via bitcoin-dev wrote: > > At this point in time it also appears the greatest risk to Taproot > dying a slow death is a small group of developers who think talking in > conservative tones and talking about endless philosophy makes Bitcoin > a conservative system. (It doesn=E2=80=99t, it just makes it a dying, dec= aying > one). The current risk to taproot and all future activations is a loud minority of users who are threatening to co-opt a LOT=3Dfalse activation by switching the parameter and organizing a marketing blitz that could end in a fork if things don't go well. As long as that threat persists consensus won't be reached. Then an activation client probably won't be released because I don't expect many devs will have an appetite for writing code that either doesn't have consensus or code that will be manipulated into creating consensus conflicts. I think Bitcoin is fine staying as is until that minority forks off with their own alt-node. If the UASF minority is dead set on creating the alt-node then I only hope it's released quickly so the deadlock can break. A quick UASF fork allows for an early LOT=3Dfalse activation. Cheers Ariel Lorenzo-Luaces > -- > Michael Folkson > Email: michaelfolkson@gmail.com > Keybase: michaelfolkson > PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3 > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev