From: "David A. Harding" <dave@dtrt.org>
To: Murch <murch@murch.one>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Motion to Activate BIP 3
Date: Tue, 18 Nov 2025 05:47:41 -1000 [thread overview]
Message-ID: <3a66dbbe9a9c46566c8a9a16ccb1cc91@dtrt.org> (raw)
In-Reply-To: <205b3532-ccc1-4b2f-964f-264fc6e0e70b@murch.one>
On 2025-11-04 15:10, Murch wrote:
> Summary of changes since BIP 3 was advanced to Proposed:
> [...]
> - that BIPs submissions may not be generated by AI/LLM⁵
> [...]
> ⁵ https://github.com/bitcoin/bips/pull/2006
I strongly disagree with this change. If I were to begin working on a
new BIP today, I would use AI throughout the process. I'd ask it to
help me create a todo list of what should go in the BIP; I'd ask it to
create a draft based on existing BIPs, my todo list, and whatever other
work products I had (e.g. prototypes); I'd then ask it to help me refine
the document until I was satisfied.
I would, of course, review every word of the draft BIP before submitting
it for consideration and ensure that it represented the highest quality
work I was able to produce---but the ultimate work would be a mix of AI
and human writing and editing.
I think considerate use of AI would be even more valuable for people who
are less comfortable with writing technical English-language documents
than I am. For example, non-native literates, people with disabilities
that make text input difficulty, and those who recognize that they're
bad writers.
The PR forbidding AI doesn't go into any detail about its motivation,
although it references a previous discussion[1] where a low-quality BIP
PR was opened using mostly AI-generated content. I'm guessing the
motivation is that AI (by itself) generates low-quality technical
content, BIPs should be high-quality technical content, and therefore we
should ban the use of AI.
However, as mentioned in the previous discussion, the BIP process
already requires high-quality content.[2] AI-generated content can be
high-quality, especially if its creation and editing was guided by a
knowledgeable human. Banning specific tools like AI seems redundant and
penalizes people who either need those tools or who can use them
effectively.
I advocate for reverting the first hunk of BIPs repository PR 2006.
-Dave
[1] https://github.com/bitcoin/bips/pull/2005
[2] "After fleshing out the proposal further and ensuring that it is of
**high quality** and properly formatted, the authors should open a pull
request to the BIPs repository." --BIP3, emphasis added
--
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/3a66dbbe9a9c46566c8a9a16ccb1cc91%40dtrt.org.
next prev parent reply other threads:[~2025-11-19 0:06 UTC|newest]
Thread overview: 31+ 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 [this message]
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-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=3a66dbbe9a9c46566c8a9a16ccb1cc91@dtrt.org \
--to=dave@dtrt.org \
--cc=bitcoindev@googlegroups.com \
--cc=murch@murch.one \
/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