From: "David A. Harding" <dave@dtrt•org>
To: Andrew Poelstra <apoelstra@wpsoftware•net>
Cc: James O'Beirne <james.obeirne@gmail•com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] CTV + CSFS: a letter
Date: Mon, 09 Jun 2025 16:08:21 -1000 [thread overview]
Message-ID: <195051b7c393b9a28727e87647ac002b@dtrt.org> (raw)
In-Reply-To: <aEdoIvOgNNtT6L4s@mail.wpsoftware.net>
On 2025-06-09 13:02, Andrew Poelstra wrote:
> if nobody in Core wants to
> engage at all with consensus changes, then the result is effectively
> the
> same as a veto.
Hi Andrew and the other signatories,
Why do you think nobody in Core wants to engage at all with consensus
changes (or, at least, specifically the proposals for CTV & CSFS)?
The usual purpose of an open letter is to generate public pressure
against the target (otherwise, if you didn't want to generate public
pressure, you would send a private letter). Does that mean that you
feel the lack of engagement is a result of a previous lack of pressure?
I have to admit that runs counter to my own sense---I thought there was
already significant social pressure on Bitcoin Core contributors to work
on CTV (and now CSFS); I wouldn't expect more pressure to achieve new
results; rather, I'd expect more pressure to create more frustration on
all sides.
Alternatively, if you feel like the lack of engagement is a result of
some other condition, I would be curious to learn of that condition and
learn why you thought an open letter (with what comes across as an
ultimatum) would help address it.
Thanks,
-Dave
--
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/195051b7c393b9a28727e87647ac002b%40dtrt.org.
next prev parent reply other threads:[~2025-06-10 2:12 UTC|newest]
Thread overview: 14+ 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 [this message]
2025-06-10 2:28 ` Melvin Carvalho
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=195051b7c393b9a28727e87647ac002b@dtrt.org \
--to=dave@dtrt$(echo .)org \
--cc=apoelstra@wpsoftware$(echo .)net \
--cc=bitcoindev@googlegroups.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