From: "David A. Harding" <dave@dtrt.org>
To: Greg Maxwell <gmaxwell@gmail.com>
Cc: Murch <murch@murch.one>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Motion to Activate BIP 3
Date: Tue, 18 Nov 2025 20:25:27 -1000 [thread overview]
Message-ID: <d0eb41a70b2ef94c2645b3f0a4b12c30@dtrt.org> (raw)
In-Reply-To: <CAAS2fgRV1aZ9xvAhBriZ=XdmYf5CvrvXWXsjVD07uynivW_qkg@mail.gmail.com>
> With outright AI 'authorship' you immediately run into potential
> copyright issues-- which I think is the origin of the "generated by"
> prohibition, otherwise I think disclosure would be sufficient.
What potential issues? I'm not familiar (and did not find in a quick
search) any authors or publishers who were sued for using content
generated by AI; all the lawsuits I found were against companies that
produced AI tools.
> the number of good submissions that could be made would hardly be
> increased by LLMs [...] but the number of potential poor submissions is
> increased astronomically. So I think it's pretty clearly a net harm to
> have text authored that way.
What evidence do you have that the number of good submissions could
hardly be increased by the use of LLMs? (Perhaps see my next point
before replying to this one.)
> I've never had an impression that drafting was at all a limiting step
> in writing BIPs
Ten years ago, I wrote the draft text for what became BIP125 because
several developers in a public Bitcoin Core IRC meeting said they
thought there should be a BIP. I think they were all hoping that
someone else would do it, and I have no way to tell if it would've been
written had I not volunteered.
I wonder if there's a hidden survivorship bias in your impression of the
situation. It's easy to think of all the great BIPs we have today---but
how many great BIPs could we have had if creating them was faster and
easier? I think many Bitcoin developers feel "better with code than
words" and only undertake documentation tasks reluctantly; if AI can
help write documentation, even just a rough draft, is that not a boon?
> I think LLMs have generally created something of an existential threat
> to most open collaborations: Now its so easy to get flooded out by
> subtly worthless material.
Is it not equally something of an existential threat to open
collaboration to deny to open collaborators the powerful tools that
closed collaborators may use? I like AI-assisted writing; my response
to BIP3 being deployed in its current form will not be to write
manually; it will be to use AI but publish elsewhere---likely a place
with fewer openly collaborating peer reviewers than the current BIPs
repo. (This is hypothetical; I have no current plans to write any
specification documents.)
-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/d0eb41a70b2ef94c2645b3f0a4b12c30%40dtrt.org.
next prev parent reply other threads:[~2025-11-19 21:45 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
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 [this message]
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=d0eb41a70b2ef94c2645b3f0a4b12c30@dtrt.org \
--to=dave@dtrt.org \
--cc=bitcoindev@googlegroups.com \
--cc=gmaxwell@gmail.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