From: Matt Corallo <lf-lists@mattcorallo•com>
To: James O'Beirne <james.obeirne@gmail•com>
Cc: Harsha Goli <harshagoli@gmail•com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] CTV + CSFS: a letter
Date: Thu, 12 Jun 2025 14:43:30 -0400 [thread overview]
Message-ID: <6a2f67ac-f273-4fef-88dd-a2dd5b20e5ff@mattcorallo.com> (raw)
In-Reply-To: <CAPfvXfLc5-=UVpcvYrC=VP7rLRroFviLTjPQfeqMQesjziL=CQ@mail.gmail.com>
On 6/12/25 2:38 PM, James O'Beirne wrote:
> Hi Matt,
>
> > Ignoring the threats in the letter
>
> There are no threats in the letter, I'm not sure why you
> think there are.
>
> > there's also a question of what the desire is - some signers specifically
> > want CTV + CSFS now, some signers are worried about "Bitcoin's ossification"
> > and just want to see progress on changes (in some cases even GCC making
> > progress may suffice!), while yet others want other specific things and
> > imagine that the politics of getting their thing will be easier once CTV +
> > CSFS happens. These all mandate drastically different responses, yet again
> > because they're all bunched into one letter we cannot figure out what it is
> > that they actually want.
>
> As the person who coordinated the letter, I can say that this is not an
> accurate characterization of the signers' intent. Everyone who signed
> explicitly wants to see the imminent review, integration, and activation
> planning for CTV+CSFS specifically. The letter is intentionally concise to make
> sure there are no misunderstandings about that.
But see this doesn't contradict what I said. Just because people think that CTV+CSFS should be
activated on some kind of accelerated timeline does not mean that they want it *because* they want
CTV+CSFS. They might (and based on my discussions some do) want it because it "prevents
ossification", or because it, in their view, unblocks progress towards something they have a more
immediate use-case for. Some, certainly, want it because they have a use for it themselves, but
others probably not so much.
Its the *why* that matters, not the ask, because, again, they all merit drastically different responses.
> I spoke to each person on the original list of signatories who either did (or
> didn't) sign and this was made very clear. Some people didn't sign as a result
> of what the letter says.
>
> The additional viewpoints you list may be shared by some signers, but the point
> of signing the letter was to signal unambiguous support for the nearterm
> integration of CTV+CSFS.
You may want to talk to Andrew Poelstra again, who on this list wrote
> My goal was to start exactly this discussion, by talking about the role
Core plays in this ecosystem and pointing to (in my view) the incentive
problems that are getting in the way of that role.
Matt
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/6a2f67ac-f273-4fef-88dd-a2dd5b20e5ff%40mattcorallo.com.
next prev parent reply other threads:[~2025-06-12 19:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 11:40 James O'Beirne
2025-06-09 12:51 ` Michael Folkson
2025-06-09 14:41 ` James O'Beirne
2025-06-09 15:56 ` Michael Folkson
2025-06-09 13:51 ` Matt Corallo
2025-06-09 14:43 ` James O'Beirne
2025-06-09 17:51 ` Matt Corallo
2025-06-09 19:27 ` /dev /fd0
2025-06-09 21:12 ` Matt Corallo
2025-06-09 18:55 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10 2:02 ` Paul Sztorc
2025-06-09 23:02 ` Andrew Poelstra
2025-06-10 2:08 ` David A. Harding
2025-06-10 13:23 ` Andrew Poelstra
2025-06-10 17:17 ` Matt Corallo
2025-06-10 23:42 ` Antoine Riard
2025-06-12 3:34 ` James O'Beirne
2025-06-13 1:18 ` Antoine Riard
2025-06-10 23:42 ` Antoine Riard
2025-06-11 13:52 ` Peter Todd
2025-06-13 6:19 ` Anthony Towns
2025-06-10 14:03 ` James O'Beirne
2025-06-10 16:56 ` Sjors Provoost
2025-06-10 17:15 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10 19:04 ` Paul Sztorc
2025-06-11 18:09 ` Brandon Black
2025-06-10 2:28 ` Melvin Carvalho
2025-06-10 13:19 ` Greg Sanders
2025-06-11 14:12 ` James O'Beirne
[not found] ` <CAB3F3Dsf8=rbOyPf1yTQDzyQQX6FAoJWTg16VC8PVs4_uBkeTw@mail.gmail.com>
2025-06-11 16:50 ` James O'Beirne
2025-06-11 18:34 ` James O'Beirne
2025-06-11 20:30 ` Matt Corallo
2025-06-12 0:59 ` Harsha Goli
2025-06-12 18:04 ` Matt Corallo
2025-06-12 18:38 ` James O'Beirne
2025-06-12 18:43 ` Matt Corallo [this message]
2025-06-12 19:51 ` Andrew Poelstra
2025-06-12 22:44 ` Matt Corallo
2025-06-13 11:08 ` Jameson Lopp
2025-06-13 12:36 ` Matt Corallo
2025-06-13 5:50 ` Anthony Towns
2025-06-12 2:06 ` Greg Maxwell
2025-06-12 3:23 ` James O'Beirne
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=6a2f67ac-f273-4fef-88dd-a2dd5b20e5ff@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=harshagoli@gmail$(echo .)com \
--cc=james.obeirne@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