From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 18 Nov 2025 17:18:12 -0800 Received: from mail-oa1-f56.google.com ([209.85.160.56]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1vLWpn-0005H9-Kk for bitcoindev@gnusha.org; Tue, 18 Nov 2025 17:18:12 -0800 Received: by mail-oa1-f56.google.com with SMTP id 586e51a60fabf-3e89ef8ac23sf1533893fac.1 for ; Tue, 18 Nov 2025 17:18:11 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1763515085; cv=pass; d=google.com; s=arc-20240605; b=QiJpkYb/gKXG5ziVVegWO13WC/4bKXy4XeSQRlJbQGmh3Api+9G3ayEmNrnf5+vAud JyEHMiTUU/GwnHmTs+9diKJFMuhjV61FNoBArzFc6aomEksECm1kO8fIdCV3vtstlx1O Lm2z7ZVa9F6COSVn59e719+KT/PdvJB6nQa3LOpB4yf/NZGK2ApHdualL2pxvK6dRwvM GKBXA0E1opXPi5DvIIC5Op5qcKBOw0ZhtJ+QRlK8JOclMaXBWnln7cMZaWRML9rfk95u NFMRyok3fScT2AC1JmCYZYu/rWhisHfLF66+ZFYQc6FvXErCcF22vgXgLw5AMwHzTxHQ iJhw== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=Mh54KbBpU4+r2fSdDOIgYwInjhPlqeqlOt+9SNXaUog=; fh=PucrOQ6uXe6zBFRQspqit+lW24A5c8TnwvMUpmwmAcA=; b=MTGiOfzH/WJCyvCshihm4pWsmSI6bFoZf9Q99JY7W6bJb0YBfLqMGBlSTDkhj6ouYT hJmGiImqOhb25jNOPZM2Um6TOO083BFlAIAGpfAW9M+eWEs2Vk1qPu4Mqwke1ntPtXjK rVgLPRnOD60gUjgDnWgqomJFs9eDBnOQlS0hr6BrsrvzIBbNa21LywyGgjbEGnix+CNr Ddz+ZLd+gF+APDW5LR+vYgHnksNPUzLSwfcgaI61E8v874lSpxPQQrWfq70n6wGttP5d 6w31WJacWGyG606shA3lujB0WPFBCmGTDBFZPOlH50hTIb3JaHTRup+GQVzrjJDz91Nv zINg==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=OujAbIdY; spf=pass (google.com: domain of gmaxwell@gmail.com designates 2607:f8b0:4864:20::434 as permitted sender) smtp.mailfrom=gmaxwell@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1763515085; x=1764119885; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:sender:from:to:cc:subject:date:message-id :reply-to; bh=Mh54KbBpU4+r2fSdDOIgYwInjhPlqeqlOt+9SNXaUog=; b=xiQgAqZTHcZaTd3D7aXKtTeEKw3Efl3Zamtku5ps6gvC+Q/0j36wD8ba5NTULdLqZY DxZ9UPowabqfObO3r5ZN71ayKrPz3Nx3AdrsZbmEpSift2VDexlWncxmYwhAiCfkp9dJ rP6z4IWScHvvGmvUfTCxdkT/2ckVoYjdnLHNtRHIREHquk/hMf4G4zXkY+EBE3/3yamv WP2TeOUdOZVQN+L2u1ONqbnKLpFCu+2yt6pLqgVR6jmMPb9GHKj9zCt1HLDFc3P47hFg 7c5GGemVTQBbNc6Z+QSzbMUFrwqdZgIXI4l/NU93zrBFzzmFZw8A/jcjVQ815D2Ets2/ IBhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763515085; x=1764119885; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Mh54KbBpU4+r2fSdDOIgYwInjhPlqeqlOt+9SNXaUog=; b=gGGT6thxUUAKoh2lf++lh9uYOEUUM/sOVqaoBqIMNoIGZ2pAqTXNH+c2Y6Z1s4sT1i gErldemqTAdjxkuinfIBIhnvD+rJZOiNdTE4pj4gbbZhNL0u0pPz1HVKCBDwzMTNTOeF Ax5wbiq6oexgE8W4WZ27TypaXWlaHnrIJCgSEu71YD6po7rAczV0KM/CBOv0FTnWwQX1 ytyA5pzzDQ2tAWb5YonoIaAbLJoUoXhdes3s+TfRPUd8Q+kl3VO1t1HWdTPtu/vpvFe6 ENFMXPK7YfP1+Xm1g0PJ+rTSjaZZXXmlcF8hye+LWErU5zB8g2S8r3jUW32Q4KJyre+U 8RbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763515085; x=1764119885; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=Mh54KbBpU4+r2fSdDOIgYwInjhPlqeqlOt+9SNXaUog=; b=nxE9aIBJooZPJ+JE77FdvxThvjEqjNmsni5VB22Vnlkzdtx/LWLwvCi3UX0ZPiPbtS J6Q/gua2rZ0FwHCFnB8vSpPo+eh/HU5LPIIDYIZOmXI8fjXTAZ+ZLgJLiuyngyMppiYX DqTHu13CGYBSi61omnzGsT7I0Fn14DUgwASm/tEfV6JwQrY9WTyJdqDY1za8jIb0DYB1 qg86U5OSdnrGv8IaZU3TF4QcCiNzAjDjIi5p4pJki52AS4aF/7PRar0a4uJnL8IIIbHI PeDjZCzfh6FKBtIPaUZfe4YFG8KdmvnYfhzIYHqdaAJvUMW0t/+0Emt2tt7fk+Ynw+Ee 5gPw== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCUNB8fETHndGV9amcNp/WveNqYzzTxwJutTzaZE9XApN4fiIfM1pDTMfB1QnUcdSx+W/IS0+GN+CS4p@gnusha.org X-Gm-Message-State: AOJu0Yx7A/So0GBHQDgWiZW+MIx1qYqFTwtRIKruHnZBt+4PbLVw5MTd fiF0SEhIrxfmMiNYnRVv+PIVj5+XBar/bnVijOdzvsy1MZglfwNI6jJD X-Google-Smtp-Source: AGHT+IEkHb1QaUfI3LmYEDJXKa95ySdKoxnxJRyHGT5NcTc0IiLzgixBn+fFiZCMrFOQOgormoQ2NA== X-Received: by 2002:a05:6870:88a9:b0:3ec:4a53:4914 with SMTP id 586e51a60fabf-3ec4a535598mr4156627fac.51.1763515084424; Tue, 18 Nov 2025 17:18:04 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com; h="Ae8XA+YYQ0UnUXgwuNHVCHJ2O1OMCxqScXDlqT/BMBoby5rovA==" Received: by 2002:a05:6871:6b15:b0:3e2:d619:f0df with SMTP id 586e51a60fabf-3e84b337ccals1721177fac.0.-pod-prod-04-us; Tue, 18 Nov 2025 17:17:59 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCV6Z0rxTXuYdWCSldpHfSFTy0WALXuxW+TjtIk06lxaBQLxib6W/KMHAuncbg/ogDR08OkAMmLYj3NL@googlegroups.com X-Received: by 2002:a05:6808:1c09:b0:44d:a531:456 with SMTP id 5614622812f47-4509758125dmr7972294b6e.52.1763515079552; Tue, 18 Nov 2025 17:17:59 -0800 (PST) Received: by 2002:a05:620a:15e:b0:8b2:e5d4:9264 with SMTP id af79cd13be357-8b302060684ms85a; Tue, 18 Nov 2025 17:12:40 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCWTtiYjJ9l7SS9krug2b8gJU2Q+AEdb3msjIQSnPZxK6bLqlJpB8H3unKpvssyLRAvx/MSXkN7QnBl8@googlegroups.com X-Received: by 2002:a05:622a:64c:b0:4ed:d76f:a350 with SMTP id d75a77b69052e-4edf2136aabmr229898931cf.75.1763514759780; Tue, 18 Nov 2025 17:12:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1763514759; cv=none; d=google.com; s=arc-20240605; b=Sc/whz6BzRTPvWDbrD60a2EhT9RP8ISTiE+IvOSqCi6YinhVG6e89MEO6nqkIICdUM uduW10+7zP4+3g2Lvf0I1xJralHzmTrr5NEBZK9OZvsufPc2DzEdu4YtFE1m/Exzj383 NSDU3a/8hGTATmK3OSgAlC25qXpmVD5EvlGoAaHBNugZoHBXa3852/kIjoINhj2GQyrt rFZzcQjL0pw01NfS12OWC2zJBkYfI0uKgEw6OlBhviMa7g8Hl7ZMA/4oFlW05vp6THk9 guy8+9dJmXprNeBJTvw19PAuvn1uFnjnY+MX3h7+9//WFuW5R+TOaY4ELeUx6+CH/M6T bZtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=kUhY4x13vLEDNNeT5YyEpyClQG0pGd933W72usMEF4Y=; fh=r98MzSXGr6be/3N8I5pSuacA3SgJZ0kDKcjdmf+Q7eg=; b=BrGcwUG16QMF4TOVZEIFUfs+o23O/rvNAtelxHdF2Cm5TRAjF25UOepxKRHr2knFS5 gwzFgjA6yQJ6QV/tpN1+5E6dw3ceZ1s4Z5ujlub4uVQHzdCih8bwRUUFxO3oQb+weTFa /kRRa6K4zVAl81Fl9FVwibxp6MuGepXsyKstxfRu1x5Vs7HGKz6merUanj4K79ZyUKdM aw8AUlrPCUSrudBxfao0kC50PNzPtlqix62TRWy8RXDZxPdmB/JumXX/5p2U9iwTTe7J qlgq3Gc4tsKUDYmg+3FLD3RyshZio6dXBlwMMuajsQOGYLrOPurk2atEw7AfZpHInm3u JpIA==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=OujAbIdY; spf=pass (google.com: domain of gmaxwell@gmail.com designates 2607:f8b0:4864:20::434 as permitted sender) smtp.mailfrom=gmaxwell@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com. [2607:f8b0:4864:20::434]) by gmr-mx.google.com with ESMTPS id d75a77b69052e-4ee0478d222si4093811cf.6.2025.11.18.17.12.39 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Nov 2025 17:12:39 -0800 (PST) Received-SPF: pass (google.com: domain of gmaxwell@gmail.com designates 2607:f8b0:4864:20::434 as permitted sender) client-ip=2607:f8b0:4864:20::434; Received: by mail-pf1-x434.google.com with SMTP id d2e1a72fcca58-7aad4823079so5663685b3a.0 for ; Tue, 18 Nov 2025 17:12:39 -0800 (PST) X-Forwarded-Encrypted: i=1; AJvYcCWKTV+9VtB/99PNegnpB1/xLa5asV3CFsc1I2O+iVQpHPxl4K7NKicIfofJKr//Sb6Kr1cH5J73lyLS@googlegroups.com X-Gm-Gg: ASbGncshR9hpL9596rEMuqijBLr3NSCiRfmV0GMGfJnBG44ldJzEATiRhv1zNvq1X8q UO5C7JfM0K2cp7GbAxAfB5MSJl1bW/16XQvY4osO2AubAzXKJhb7VTULcxQ8wkKzAKtVy5qTZ/P yA+AAJqK3qK2f5BLCHK23zu0AQcuyg1uY/LmLsPtx28tR4AvR5FHYT/WgJv4GyoEtbjx8dD0dNw /ZNqwlzEtAIdoxddb7dshPwSAe5+2/IPpCgQh5n1rHfsUgyX71In6oKAeiB+bNL2jM6o74DCcfw 1u1djVjkZEhvtgHmHS/4hCAo1e2NXh+G1FRh8fRhm+zWNLbWM33kK1JY/BWHUw== X-Received: by 2002:a05:7022:68a3:b0:11a:2ec8:de1c with SMTP id a92af1059eb24-11b4130b653mr9662840c88.36.1763514758841; Tue, 18 Nov 2025 17:12:38 -0800 (PST) MIME-Version: 1.0 References: <205b3532-ccc1-4b2f-964f-264fc6e0e70b@murch.one> <3a66dbbe9a9c46566c8a9a16ccb1cc91@dtrt.org> In-Reply-To: <3a66dbbe9a9c46566c8a9a16ccb1cc91@dtrt.org> From: Greg Maxwell Date: Wed, 19 Nov 2025 01:12:27 +0000 X-Gm-Features: AWmQ_bm-KNZIYNYzZpfOkB_ey7hRGhLeHNGK-G5DCTJpNHBIVEsKFuaTRBjpPn4 Message-ID: Subject: Re: [bitcoindev] Motion to Activate BIP 3 To: "David A. Harding" Cc: Murch , bitcoindev@googlegroups.com Content-Type: multipart/alternative; boundary="000000000000c1c9300643e84613" X-Original-Sender: gmaxwell@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=OujAbIdY; spf=pass (google.com: domain of gmaxwell@gmail.com designates 2607:f8b0:4864:20::434 as permitted sender) smtp.mailfrom=gmaxwell@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) --000000000000c1c9300643e84613 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No doubt *you* are able to make good documents with or without the aid of AI. 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. Taking a step back: is Bitcoin's welfare maximized by permitting LLM glurge submissions in standards documents? In some cases it's benign, I readily agree, in others its harmful. But the number of good submissions that could be made would hardly be increased by LLMs (being limited by expert proposers with good ideas) 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. I've never had an impression that drafting was at all a limiting step in writing BIPs, though even to the extent that it has been at times it's possible to use LLMs in a review capacity to make authorship much easier ("What's missing / unclear?") without resorting to using it to author. There is a particularly clear pattern at least with current LLM tools that users who lack the skills to have authored the work without an LLM are generally unable to recognize when the LLM is full of crap (and even sometimes when they should know better), so unfortunately they're only benign to use in the hands of those whose need is the least. And as a reviewer outside of Bitcoin I've found LLM powered proposers to be absolutely the worst to deal with. Because they're not submitting their own words and ideas, they're unable to change their thinking in response or explain sufficiently to change yours--- the interactions often degrade to them just copy and pasting their chatbot back to you. Because it's cheap to generate more text they also tend to flood you out with documents several times longer than any human author would have bothered with. 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. Many projects, including, Bitcoin have long struggled with review capacity being limited and a far amount of time waste by thoughtless (or even crazy!) submissions, but now it's automated and even the most well meaning person may now make submissions that are as bad as the most deviously constructed malicious submissions could have been in the past, not even know they are doing it, and can make a dozen proposals before lunch without even breaking a sweat. On Wed, Nov 19, 2025 at 12:06=E2=80=AFAM David A. Harding w= rote: > On 2025-11-04 15:10, Murch wrote: > > Summary of changes since BIP=E2=80=AF3 was advanced to Proposed: > > [...] > > - that BIPs submissions may not be generated by AI/LLM=E2=81=B5 > > [...] > > =E2=81=B5 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/3a66dbbe9a9c46566c8a9a16ccb1= cc91%40dtrt.org > . > --=20 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 e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= CAAS2fgRV1aZ9xvAhBriZ%3DXdmYf5CvrvXWXsjVD07uynivW_qkg%40mail.gmail.com. --000000000000c1c9300643e84613 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No doubt *you* are able to make good documents with o= r without the aid of AI.

With outright AI 'aut= horship' you immediately run into potential=20 copyright issues-- which I think is the origin of the "generated by&qu= ot;=20 prohibition, otherwise I think disclosure would be sufficient.
Taking a step back: is Bitcoin's welfare=C2=A0maximized by= permitting LLM glurge submissions in standards documents? In some cases it= 's benign, I readily agree, in others its harmful.=C2=A0 But the number= of good submissions that could be made would hardly be increased by LLMs (= being limited by expert proposers with good ideas) but the number of potent= ial poor submissions is increased astronomically.=C2=A0 So I think it's= pretty clearly a net harm to have text authored that way.

I've never had an impression that drafting was at all a limiti= ng step in writing BIPs, though even to the extent that it has been at time= s it's possible to use LLMs in a review capacity to make authorship muc= h easier ("What's missing / unclear?") without resorting to u= sing it to author.

There is a particularly clear pattern at l= east with current LLM tools that users who lack the skills to have authored= the work without an LLM are generally unable to recognize when the LLM is = full of crap (and even sometimes when they should know better), so unfortun= ately they're only benign to use in the hands of those whose need is th= e least.=C2=A0=C2=A0

And as a reviewer outside of = Bitcoin I've found LLM powered proposers to be absolutely the worst to = deal with. Because they're not submitting their own words and ideas, th= ey're unable to change their thinking in response or explain sufficient= ly to change yours--- the interactions often degrade to them just copy and = pasting their chatbot back to you.=C2=A0 Because it's cheap to generate= more text they also tend to flood you out with documents several times lon= ger than any human author would have bothered with.

I think LLMs have generally created something of an existential threat to= most open collaborations: Now its=C2=A0so easy to get flooded out by subtl= y worthless material.=C2=A0 Many projects, including, Bitcoin have long str= uggled with review capacity being limited and a far amount of time waste by= thoughtless (or even crazy!) submissions, but now it's automated and e= ven the most well meaning person may now make submissions that are as bad a= s the most deviously constructed malicious submissions could have been in t= he past, not even know they are doing it, and can make a dozen proposals be= fore lunch without even breaking a sweat.



On Wed, Nov 19, 2025 at 12:06=E2=80=AFAM David A. H= arding <dave@dtrt.org> wrote:
On 2025-11-04 15:1= 0, Murch wrote:
> Summary of changes since BIP=E2=80=AF3 was advanced to Proposed:
> [...]
> =C2=A0 - that BIPs submissions may not be generated by AI/LLM=E2=81=B5=
> [...]
> =E2=81=B5 https://github.com/bitcoin/bips/pull/2006

I strongly disagree with this change.=C2=A0 If I were to begin working on a=
new BIP today, I would use AI throughout the process.=C2=A0 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 refin= e
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.=C2=A0 For example, non-native literates, people with disabilitie= s
that make text input difficulty, and those who recognize that they're <= br> bad writers.

The PR forbidding AI doesn't go into any detail about its motivation, <= br> although it references a previous discussion[1] where a low-quality BIP PR was opened using mostly AI-generated content.=C2=A0 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]=C2=A0 AI-generated content can be=
high-quality, especially if its creation and editing was guided by a
knowledgeable human.=C2=A0 Banning specific tools like AI seems redundant a= nd
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 o= f
**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 &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/3a66dbbe9a9c= 46566c8a9a16ccb1cc91%40dtrt.org.

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/= msgid/bitcoindev/CAAS2fgRV1aZ9xvAhBriZ%3DXdmYf5CvrvXWXsjVD07uynivW_qkg%40ma= il.gmail.com.
--000000000000c1c9300643e84613--