From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Follow-up regarding Motion to Activate BIP 3
Date: Tue, 6 Jan 2026 16:42:26 -0800 [thread overview]
Message-ID: <1d76a085-deff-4df2-8a82-f8bd984fac27@murch.one> (raw)
Dear colleagues,
In early November, I asked whether there was support for adopting BIP 3
as the guideline for the BIPs Process.
In response, about a dozen respondents stated support for activating
BIP 3. Some respondents raised concerns that resulted in changes to the
BIP or otherwise were addressed here on the mailing list. The adopted
changes were summarized here on the mailing list (see
https://groups.google.com/g/bitcoindev/c/j4_toD-ofEc/m/esV-XScYAAAJ). A
few respondents seemed to imply general support, but requested reversal
of the recently introduced LLM-policy, which has since been implemented.
As there was no further follow-up to raised concerns in over three
weeks, I posit that the concerns have been addressed satisfactorily.
In detail, Ava Chow, David Gumberg, Jon Atack, Jonas Nick, Gloria Zhao,
Michael Ford, Ruben Somsen, Greg Sanders, and Antoine Poinsot explicitly
stated support for activating BIP 3 before the amendment.
Pieter Wuille supported activation conditional on the reversal of the
LLM-guidance.
Concerns by David Harding, Luke Dashjr, and Melvin Carvalho have been
addressed.
The amended proposal has been explicitly endorsed (again) by AJ Towns,
Tim Ruffing, and Pol Espinasa after the December 15th update.
It is my perception that among those that commented, support for
activation significantly outweighed rejection, and that all concerns
have been addressed. As Melvin Carvalho pointed out, that I, as the
Author of the proposal, should not be the one to assess whether BIP 3
has rough consensus. I therefore request that others, especially
participants in the BIPs process, comment on whether they perceive there
to be rough consensus for activating BIP 3.
Thanks,
Murch
--
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/1d76a085-deff-4df2-8a82-f8bd984fac27%40murch.one.
next reply other threads:[~2026-01-07 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 0:42 Murch [this message]
2026-01-08 20:40 ` Chris Stewart
2026-01-09 14:11 ` Coperbyte Solutions
2026-01-12 12:35 ` Jonas Nick
2026-01-13 1:16 ` Murch
2026-01-14 0:06 ` Ruben Somsen
2026-01-14 0:47 ` Bryan Bishop
2026-01-14 8:27 ` Tim Ruffing
2026-01-14 19:12 ` Murch
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=1d76a085-deff-4df2-8a82-f8bd984fac27@murch.one \
--to=murch@murch.one \
--cc=bitcoindev@googlegroups.com \
/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