From: Peter Todd <pete@petertodd•org>
To: Zac Greenwood <zachgrw@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Zac Greenwood via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>,
Keagan McClelland <keagan.mcclelland@gmail•com>
Subject: Re: [bitcoin-dev] User Resisted Soft Fork for CTV
Date: Sun, 24 Apr 2022 16:47:47 +0200 [thread overview]
Message-ID: <B037C028-EB25-4197-A0F1-48838D1AD30F@petertodd.org> (raw)
In-Reply-To: <CAJ4-pEADrHf_YR5ZBfJW+eefKrp1iEj4wAi72UrwRSi9gaVP+w@mail.gmail.com>
On April 22, 2022 11:03:51 AM GMT+02:00, Zac Greenwood via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>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 “free” eternal storage on
>the blockchain.
To strengthen your point: benefiting "all users" can only be done by benefiting layer 2 solutions in some way, because it's inevitable that the vast majority of users will use layer 2 because that's the only known way that Bitcoin can scale.
next prev parent reply other threads:[~2022-04-24 14:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 16:45 Michael Folkson
2022-04-21 23:36 ` Keagan McClelland
2022-04-22 9:03 ` Zac Greenwood
2022-04-22 15:40 ` Corey Haddad
2022-04-23 5:07 ` Billy Tetrud
2022-04-23 14:48 ` Erik Aronesty
2022-04-24 14:47 ` Peter Todd [this message]
2022-04-25 5:36 ` ZmnSCPxj
2022-04-25 9:06 ` Zac Greenwood
2022-04-25 10:01 ` ZmnSCPxj
2022-04-22 9:53 ` Michael Folkson
2022-04-23 20:40 ` Jorge Timón
2022-04-24 12:17 ` Michael Folkson
2022-04-24 12:57 ` Jorge Timón
2022-04-24 12:55 ` Ryan Grant
2022-04-24 13:11 ` Jorge Timón
2022-04-24 13:15 ` Ryan Grant
2022-04-25 16:11 alicexbt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B037C028-EB25-4197-A0F1-48838D1AD30F@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=keagan.mcclelland@gmail$(echo .)com \
--cc=zachgrw@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox