From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Motion to Activate BIP 3
Date: Mon, 15 Dec 2025 16:24:04 -0800 [thread overview]
Message-ID: <fa4610d6-ba6b-485c-8fa0-710d45a684a4@murch.one> (raw)
In-Reply-To: <378db30d-774c-451c-bf18-c0084b7615d0@murch.one>
Hi everyone,
the pull request implementing the feedback from this thread was merged
today. The PR adopted many of the suggestions provided here. I believe
that the other issues and concerns have been addressed by me and others
in this thread. I would like to highlight especially that the recently
added guidance regarding AI/LLM use was reverted, a Changelog was added
to BIP 3, and the process for number assignment was slightly clarified.
In total, the PR had twelve commits titled as follow:
3d07d12 Revert "BIP3: add guidance on originality, quality, LLMs"
56ac1c2 bip3: Broaden reference implementation formats
6f62034 bip3: Clarify editor assignment of BIP numbers
25810a0 bip3: Avoid implying BIP editors must reply to every ML post
e44d11e bip3: Clarify that draft needs to be discussed on ML
86d9737 bip-0003: Move Type header responsibility to the author(s)
5fd4162 bip-0003: Changes from BIP 2: Make it match actual spec
f29514f bip3: Fix capitalization and drop footnote
f389e9b bip3: Avoid onus
41fe83f bip3: Add and backfill Changelog section
a9308f3 bip3: Require technical soundness
897fa1b bip3: Do not waste community’s time
You can find the changes in detail in the PR:
https://github.com/bitcoin/bips/pull/2051
I will now be working on bringing the activation PR back up-to-date (see
https://github.com/bitcoin/bips/pull/1820), as I turn the conversation
back over to you, to assess whether all concerns have been addressed
satisfactorily and whether BIP 3 has rough consensus for activating.
Thanks,
Murch
On 2025-12-09 16:56, Murch wrote:
> Hey all,
>
> Thank you for your ardent review and discussion. I have read and
> processed all emails in this thread. In conclusion, I have opened a pull
> request that:
>
> - reverts the recently added guidance regarding AI/LLM use
> - adds a Changelog
> - adopts some of the suggestions from Luke’s review as indicated by my
> replies here and on his pull request in the BIPs Repository (#2037)
>
> Should anyone want to take another stab at providing guidance regarding
> use of AI/LLM, I would like to suggest that such a proposal be tackled
> after activation of BIP 3.
>
> I am looking forward to your review, and hope that you find that between
> my responses here and the changes proposed in the pull request all
> comments have been addressed adequately.
> Please find the pull request here: https://github.com/bitcoin/bips/
> pull/2051
>
> Best,
> 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/fa4610d6-ba6b-485c-8fa0-710d45a684a4%40murch.one.
next prev parent reply other threads:[~2025-12-16 0:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 1:10 Murch
2025-11-05 1:53 ` Ruben Somsen
2025-11-12 19:03 ` [bitcoindev] " Greg Sanders
2025-11-13 0:23 ` Murch
2025-11-13 18:54 ` Greg Sanders
[not found] ` <Qe_CRlsuwalN-0a0oo1KcZ265rXevTeHaTdk6IifH-j7NbLMew7-ucLLMiwECQLZEPoU2pm-PAuwb_lZAeCU9vChaVYTZzl60N9jyPTnUbo=@protonmail.com>
2025-11-13 19:35 ` [bitcoindev] " 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-11-13 21:43 ` Murch
2025-11-14 17:05 ` Melvin Carvalho
2025-11-22 23:46 ` Murch
2025-11-29 23:00 ` Melvin Carvalho
2025-12-02 0:29 ` Murch
2025-11-15 22:01 ` Luke Dashjr
2025-11-18 4:26 ` Greg Maxwell
2025-12-02 22:46 ` Murch
2025-11-18 15:47 ` David A. Harding
2025-11-19 1:12 ` Greg Maxwell
2025-11-19 1:20 ` Bryan Bishop
2025-11-19 21:21 ` Jon Atack
2025-11-19 6:25 ` David A. Harding
2025-11-19 6:58 ` Bitcoin Error Log
2025-11-20 1:22 ` Bitcoin Mechanic
2025-11-20 9:06 ` Oghenovo Usiwoma
2025-11-20 17:23 ` Greg Maxwell
2025-11-22 15:14 ` Jon Atack
2025-11-22 19:30 ` Sjors Provoost
2025-11-22 20:53 ` /dev /fd0
2025-11-28 15:35 ` Tim Ruffing
2025-11-28 16:34 ` Jon Atack
2025-11-28 19:21 ` Pieter Wuille
2025-12-10 0:56 ` Murch
2025-12-16 0:24 ` Murch [this message]
2025-11-22 21:06 ` Bill MacDonald
2025-11-20 20:14 ` Mat Balez
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=fa4610d6-ba6b-485c-8fa0-710d45a684a4@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