From: Zac Greenwood <zachgrw@gmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] User Resisted Soft Fork for CTV
Date: Mon, 25 Apr 2022 11:06:09 +0200 [thread overview]
Message-ID: <CAJ4-pEB1zWxWapt3qit=X1p3WuSSn2_K=rygDp8JzpS7GimgMg@mail.gmail.com> (raw)
In-Reply-To: <tBEO_7gKqAlgiRpjC1OCLMBcLddK0ffNlbdU65VhXnXqZQiDCTDNOw8sfTXqNXZxVA8wA0uodTLvptt7Iy5O3D_6hkiVVfLegOrg9C1Snkg=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On Mon, 25 Apr 2022 at 07:36, ZmnSCPxj <ZmnSCPxj@protonmail.com> wrote
CTV *can* benefit layer 2 users, which is why I switched from vaguely
> apathetic to CTV, to vaguely supportive of it.
Other proposals exist that also benefit L2 solutions. What makes you
support CTV specifically?
Centrally documenting the implications of each side by side and point by
point might be a useful next step. This would enable a larger part of the
community to understand each proposal and may reduce repetition and
misunderstandings on this list.
Once a common understanding of the implications of each proposal is in
place, their tradeoffs can be considered, facilitating creating consensus
on which proposal benefits a maximum of users.
Zac
[-- Attachment #2: Type: text/html, Size: 1270 bytes --]
next prev parent reply other threads:[~2022-04-25 9:06 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
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 [this message]
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='CAJ4-pEB1zWxWapt3qit=X1p3WuSSn2_K=rygDp8JzpS7GimgMg@mail.gmail.com' \
--to=zachgrw@gmail.com \
--cc=ZmnSCPxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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