From: alicexbt <alicexbt@protonmail•com>
To: "zachgrw@gmail•com" <zachgrw@gmail•com>,
"pete@petertodd•org" <pete@petertodd•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] User Resisted Soft Fork for CTV
Date: Mon, 25 Apr 2022 16:11:11 +0000 [thread overview]
Message-ID: <fcK27N_8spjOw3tOQvck5WiEw207k7GYQcehAb1vlnMHNk0pOSdg3IcaFyKgZuqWRlBlC3oi_f-x5y7kfvTStvqB2eFBf-abRygVT7Cl4bo=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]
Hi Peter and Zac,
> 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.
- CTV does not allow bitcoin blockchain to be used as storage
- CTV will benefit layer 2 solutions: lightning, sidechains, spacechain etc.
- Every L2 is dependent on L1 and soft forks could improve things that benefit both
There are a few emails with information that could be interpreted in a wrong way on this mailing list related to CTV or creating contentious environment. I had expected better things from bitcoin developers. This is not just the opinion of someone who supports CTV but even people who are trying to read things and form an opinion: https://nitter.net/NicolasDorier/status/1518407535480705024
I am sure there are lot of positives if we look at things differently and will end the email on a good note:
You might like Jeremy or hate him, however he took some real efforts in working on CTV, Sapio etc. and even if BIP 119 never gets activated his contribution in bitcoin covenants will always be appreciated.
/dev/fd0
Sent with [ProtonMail](https://protonmail.com/) secure email.
[-- Attachment #2: Type: text/html, Size: 2389 bytes --]
next reply other threads:[~2022-04-25 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 16:11 alicexbt [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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='fcK27N_8spjOw3tOQvck5WiEw207k7GYQcehAb1vlnMHNk0pOSdg3IcaFyKgZuqWRlBlC3oi_f-x5y7kfvTStvqB2eFBf-abRygVT7Cl4bo=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)org \
--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