From: Brandon Black <freedom@reardencode•com>
To: Sjors Provoost <sjors@sprovoost•nl>
Cc: James O'Beirne <james.obeirne@gmail•com>,
Andrew Poelstra <apoelstra@wpsoftware•net>,
"David A. Harding" <dave@dtrt•org>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] CTV + CSFS: a letter
Date: Wed, 11 Jun 2025 11:09:24 -0700 [thread overview]
Message-ID: <aEnGVB5vlUrz66OL@console> (raw)
In-Reply-To: <0B7CEBEE-FB2B-41CF-9347-B9C1C246B94D@sprovoost.nl>
Hi Sjors,
On 2025-06-10 (Tue) at 18:56:54 +0200, Sjors Provoost wrote:
> From both your and Andrew's mail we can distill a relevant factor: pretty much everyone who is excited about (feature) soft forks is not working on Bitcoin Core.
>
> A few, such as yourself and Jeremy, were in the past but stopped doing so.
>
> Although trying to persuade more people inside the project to review and further develop these proposals is useful - methods and tone tbd - also consider the opposite: convince more people who want these changes to start contributing to Bitcoin Core.
[...]
> 1. It takes years to ramp up. The best time to plant a tree is ten years ago. But it's been six years and multiple developers could have been ramped up by now. To be fair, grant budgets were pretty tight until only two years ago.[1]
You might notice that there's a strong correlation of new developers
interested in potentially making improvements to bitcoin's consensus
rules _not_ investing the years to ramp up on the project starting about
the same time that the CTV and APO proposals were abandoned.
This open letter reflects the reality that if none of the central
members of a project are working in the direction that an enthusiastic
outsider is interested in pursuing it is approximately impossible for
that outsider to ramp up on the project and reasonably hope to achieve
their goals.
I have not discussed this with other signatories to the letter, but I
suspect that a commitment to mentor and support developers working on
consensus improvements from the broader bitcoin core project would also
constitute a satisfactory response.
While we the signatories believe that CTV+CSFS is a positive direction
for consensus improvements on bitcoin, I don't think any of us would say
that it is the only possible positive consensus improvement. The primary
thrust of this letter is that consensus improvements should be
prioritized alongside other work on bitcoin core. In an environment
where consensus improvements were given equal billing to relay, p2p,
build system, refactoring and other current project priorities this
letter would never have been authored, signed, nor published.
Fond regards,
--Brandon
--
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/aEnGVB5vlUrz66OL%40console.
next prev parent reply other threads:[~2025-06-12 0:02 UTC|newest]
Thread overview: 38+ 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-10 23:42 ` Antoine Riard
2025-06-11 13:52 ` Peter Todd
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 [this message]
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
2025-06-12 19:51 ` Andrew Poelstra
2025-06-12 22:44 ` Matt Corallo
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=aEnGVB5vlUrz66OL@console \
--to=freedom@reardencode$(echo .)com \
--cc=apoelstra@wpsoftware$(echo .)net \
--cc=bitcoindev@googlegroups.com \
--cc=dave@dtrt$(echo .)org \
--cc=james.obeirne@gmail$(echo .)com \
--cc=sjors@sprovoost$(echo .)nl \
/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