From: Corey Haddad <corey3@gmail.com>
To: Zac Greenwood <zachgrw@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] User Resisted Soft Fork for CTV
Date: Fri, 22 Apr 2022 11:40:19 -0400 [thread overview]
Message-ID: <CAK_HAC8UrPSDoYU-b4KrZqGF3ndWqobPu2y_ddmCvTqNsbifBw@mail.gmail.com> (raw)
In-Reply-To: <CAJ4-pEADrHf_YR5ZBfJW+eefKrp1iEj4wAi72UrwRSi9gaVP+w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]
>*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*.*
This manages to be both incorrect and philosophically opposed to what
defines success of the project . Neither the number of ways that people
figure out how to innovatively harness Bitcoin's existing capabilities, nor
the number or complexity of any optional transaction types that the Bitcoin
protocol supports have any bearing on transaction fees. Demand for
blockspace from transactions, which is just plain *use* - and not *use
cases* - is what could drive up transaction fees.
On the philosophical level, as designers of the system, we all hope and
work to make Bitcoin so useful, appealing, and secure that there is massive
demand for blockspace, even in the face of high transaction fees. As an
individual thinking only of their next on-chain transaction, it is
understandable that one might hope for low fees and partially-filled
blocks. Longer term, the health of the system can both be measured by and
itself depends on high transaction demand and fee pressure.
If you were trying to argue that CTV is invasive because it may increase
transaction demand and therefore cost users more fees, that is 1) an
endorsement of CTV's desirability and 2) reveals that you consider any
increased free-market competition (i.e. more demand) to be "invasive".
*>I like the maxim of Peter Todd: any change of Bitcoin must benefit *all*
users. *
As for Peter Todd's "any change of Bitcoin must benefit *all* users", that
is absolutely a reasonable thing to consider. However, in order to make
practical use of that maxim, we must adopt in our minds a *generic*, or
"model user", and then replicate them so that we may meaningfully
understand a least a proxy for "all users". In reality, there will always
be someone (and at this point, probably a "user" too) who wouldn't benefit
from a change, or at least think they won't. Some users of Bitcoin may even
want Bitcoin to fail, so we cannot afford assume that people have alignment
of goals or vision just by virtue of being a 'user'.
Corey
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3220 bytes --]
next prev parent reply other threads:[~2022-04-22 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 16:45 [bitcoin-dev] User Resisted Soft Fork for CTV Michael Folkson
2022-04-21 23:36 ` Keagan McClelland
2022-04-22 9:03 ` Zac Greenwood
2022-04-22 15:40 ` Corey Haddad [this message]
2022-04-23 5:07 ` Billy Tetrud
2022-04-23 14:48 ` Erik Aronesty
2022-04-24 14:47 ` Peter Todd
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=CAK_HAC8UrPSDoYU-b4KrZqGF3ndWqobPu2y_ddmCvTqNsbifBw@mail.gmail.com \
--to=corey3@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=zachgrw@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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