From: Matt Corallo <lf-lists@mattcorallo•com>
To: 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:04:41 -0400 [thread overview]
Message-ID: <8d158e3d-b3cc-44b6-b71b-ab2e733c047c@mattcorallo.com> (raw)
In-Reply-To: <de023ffa-6f8b-44bc-8e4d-6012e2ba3ccen@googlegroups.com>
On 6/11/25 8:59 PM, Harsha Goli wrote:
> Quickly chiming in here. I'm digging in heavily to the different needs and drivers of businesses and
> individuals in the space. I think James is being quite literal here. There is not unity on what
> should happen after if we reach 2026 without any progress on covenants.
>
> Not speaking for James, but from what I've seen there is no substance or chatter regarding any such
> "vague threat".
I do think this highlights why sign-on letters tend to have little impact and are really quite
useless for this kind of thing: when you actually go talk to people, you come away understanding
that they have very different views on the issue at hand.
Some signers appear to have intention to release an "activation client", meanwhile when I talk to
other signers they're really just trying to encourage more focused research on things in this area.
Those are *drastically* different views, yet both are "covered" by the same letter.
Worse yet, there's now organizations signing this letter (yay NYA reprisal!), which similarly cannot
possibly be filled with people with identical views (of course organizations themselves cannot opine
on technical bitcoin decisions, individuals do, there is good reason why organizations do not have a
role within IETF, only engineers expressing their own opinions, which may benefit their organization).
Ignoring the threats in the letter, 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.
Instead, and I've encouraged various people who've signed to do this, having engineers who wish to
utilize these features speak up about what, specific, tools and protocols they wish to build using
CTV + CSFS would be much more interesting. Unlike a generic "We Want Things" sign-on letter,
individual messages indicating desire to utilize features is way more compelling, not just to
overall impression of Bitcoin's consensus, but also to the individuals deciding what to do with
their time - now you can see actual real-world desires.
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/8d158e3d-b3cc-44b6-b71b-ab2e733c047c%40mattcorallo.com.
next prev parent reply other threads:[~2025-06-12 18:06 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 [this message]
2025-06-12 18:38 ` James O'Beirne
2025-06-12 18:43 ` Matt Corallo
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=8d158e3d-b3cc-44b6-b71b-ab2e733c047c@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=harshagoli@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