Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 734FAC002D for ; Fri, 22 Apr 2022 09:04:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 50D9E40CCB for ; Fri, 22 Apr 2022 09:04:03 +0000 (UTC) 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 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 Oav4b4TS166e for ; Fri, 22 Apr 2022 09:04:02 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) by smtp2.osuosl.org (Postfix) with ESMTPS id AB10940CCA for ; Fri, 22 Apr 2022 09:04:02 +0000 (UTC) Received: by mail-io1-xd2d.google.com with SMTP id q22so7983431iod.2 for ; Fri, 22 Apr 2022 02:04:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=bNyeO5CirjxOzTJgoHv7PZ83OChrpWqQllZQ/xY5rbo=; b=VDdUyRGGV1HjKUJe7wMD4yO2FQYcs0eR+Ob0jvaUv5PkPqxImJlZaaARAxbm5AvnGo XaZDsd9nyE3Z/453f8Jp3w4nE+T6Kmptv9hllEDF4O3OPE7DJzVb3OsKvZCBgdAw+ksX XREiWNSvOkWskmE4UxX1o9j6Ioqfc0pUydoygzcHusnJ2UoL+WWW0cxxVdkDZM8vpGDK UuvrlEHafiz4SvM+24w6EmWiX0QanH9JvwCm8bab8xENHygWwgkkwevmkLJQIdskg3MI VI2JAUPtAkkz74+U3rcwENxI79Lr26WFBmqiscFMC17i7bQS7odksuRZqHstlgDiFMtF 7xvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=bNyeO5CirjxOzTJgoHv7PZ83OChrpWqQllZQ/xY5rbo=; b=1PJLmDw4J3xFytSwwUWQS/oIlA8WvcxHpyR6nDvBhIITuFDJ5RakPIVTT6/QRwoySn pLqHa0qH5CLGikdVQx7AmHvkeK5YfpsJNE+7Q/bDl2rJK4EQygcLRT5LrZkF0BugWeUk yUEoSaG7rVozsaRsQdSizTtDON7uyU4hwXdHvmjTmm40EbcS3HhlxHHi0qvfVNByzutw OyPrcqDp+CfOf1YGni2fjsrSofns8us+DIcuxB4ssTlmthJkuXo74aRzEoJlOQm0arv4 tQotBBEbOa5Y775v48fxCtYaK0VP9OvDXPbq81Om8oRRghko27+fw6nOKF2l2a63uB2c +EcQ== X-Gm-Message-State: AOAM533Rhm2RrY8AH+lELy8w3XbereUMb6I8BRbqRJimyrjmIhEpH2w0 YIqrn8sjhA4MDk7hVff7H0Q74Neu+JYsZAEv6ByUKvovyyE= X-Google-Smtp-Source: ABdhPJyMvkXuUam8Qt6fh7c6IvNOdcG4zKvWUh4p3MtdrrOuYXj0IxIs40C7h74V781BDH6dCdkykkdaZFoy8MkuBkA= X-Received: by 2002:a05:6638:14d5:b0:323:dca6:fe8a with SMTP id l21-20020a05663814d500b00323dca6fe8amr1576410jak.309.1650618241765; Fri, 22 Apr 2022 02:04:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Zac Greenwood Date: Fri, 22 Apr 2022 11:03:51 +0200 Message-ID: To: Bitcoin Protocol Discussion , Keagan McClelland Content-Type: multipart/alternative; boundary="000000000000f5d61e05dd3a8103" X-Mailman-Approved-At: Fri, 22 Apr 2022 09:15:28 +0000 Subject: Re: [bitcoin-dev] User Resisted Soft Fork for CTV 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: Fri, 22 Apr 2022 09:04:03 -0000 --000000000000f5d61e05dd3a8103 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 22 Apr 2022 at 09:56, Keagan McClelland via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > I think that trying to find ways to activate non-invasive changes should > be everyone's goal, *even if* they personally may not have an immediate u= se > case > A change that increases the number of use cases of Bitcoin affects all users and is *not* non-invasive. More use cases means more blockchain usage which increases the price of a transaction for *everyone*. I like the maxim of Peter Todd: any change of Bitcoin must benefit *all* users. This means that every change must have well-defined and transparent benefits. Personally I believe that the only additions to the protocol that would still be acceptable are those that clearly benefit layer 2 solutions such as LN *and* do not carry the dangerous potential of getting abused by freeloaders selling commercial services on top of =E2=80=9Cfree=E2=80=9D et= ernal storage on the blockchain. Zac > --000000000000f5d61e05dd3a8103 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, 22 Apr 2022 at 09:56, Keagan McClelland via bitcoin-dev <bitcoin-dev@lists.li= nuxfoundation.org> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rg= b(204,204,204)">
I think that trying to f= ind ways to activate non-invasive changes should be everyone's goal, *e= ven if* they personally may not have an immediate use case

A change that increas= es the number of use cases of Bitcoin affects all users and is *not* non-in= vasive. More use cases means more blockchain usage which increases the pric= e of a transaction for *everyone*.

I like the maxim of Peter Todd: any change of Bitcoin must benef= it *all* users. This means that every change must have well-defined and tra= nsparent benefits. Personally I believe that the only additions to the prot= ocol that would still be acceptable are those that clearly benefit layer 2 = solutions such as LN *and* do not carry the dangerous potential of getting = abused by freeloaders selling commercial services on top of =E2=80=9Cfree= =E2=80=9D eternal storage on the blockchain.

Zac
--000000000000f5d61e05dd3a8103--