Motion to Activate BIP 3

Nov 5 - Dec 2, 2025

  • In a recent development within the Bitcoin Improvement Proposal (BIP) process, discussions have been centered around the role of Artificial Intelligence (AI) and Large Language Models (LLMs) in drafting BIPs.

A pull request has been opened by an active member, Murch, addressing several points raised during these discussions. The key actions taken include reverting the guidance that was recently added regarding the use of AI/LLM in creating BIP content. This decision reflects the community's ongoing debate about how to effectively integrate AI tools without compromising the quality and integrity of BIP submissions.

Furthermore, the introduction of a Changelog aims to enhance transparency and provide a clear record of changes made to proposals, particularly after they reach the "Complete" or "Deployed" status. This addition is part of a broader effort to ensure that the evolution of BIPs is well-documented and accessible to all stakeholders within the Bitcoin development community.

The pull request also incorporates suggestions from a comprehensive review conducted by another community member, Luke, highlighting the collaborative nature of refining the BIP process. Some of these adopted suggestions were detailed in the exchanges on Luke’s own pull request in the BIPs Repository (2037), showcasing the dynamic and responsive framework under which Bitcoin governance operates.

Murch's call for further input on the use of AI/LLM post-activation of BIP 3 suggests an openness to revisiting this complex issue in the future. This stance acknowledges the potential benefits of AI tools in streamlining and enhancing the proposal drafting process, while also recognizing the need for careful consideration of their implications.

The pull request, available for community review at PR 2051, marks a significant step towards addressing the concerns and ideas raised by contributors. It underscores the commitment to maintaining a rigorous, inclusive, and adaptable approach to BIP development, ensuring that the process remains reflective of the community's values and technical standards.

Link to Raw Post

Thread Summary (30 replies)

Nov 5 - Dec 2, 2025

Message History

31 messages

MurchOriginal Post
Nov 5, 2025/01:10 UTC
Ruben Somsen
Nov 5, 2025/01:53 UTC
Greg Sanders
Nov 12, 2025/19:03 UTC
Murch
Nov 13, 2025/00:23 UTC
Greg Sanders
Nov 13, 2025/18:54 UTC
Antoine Poinsot'
Nov 13, 2025/19:35 UTC
Murch
Nov 13, 2025/21:43 UTC
Melvin Carvalho
Nov 14, 2025/17:05 UTC
Luke Dashjr
Nov 15, 2025/22:01 UTC
Greg Maxwell
Nov 18, 2025/04:26 UTC
David A. Harding
Nov 18, 2025/15:47 UTC
Greg Maxwell
Nov 19, 2025/01:12 UTC
Bryan Bishop
Nov 19, 2025/01:20 UTC
David A. Harding
Nov 19, 2025/06:25 UTC
Bitcoin Error Log
Nov 19, 2025/06:58 UTC
Jon Atack
Nov 19, 2025/21:21 UTC
Bitcoin Mechanic
Nov 20, 2025/01:22 UTC
Oghenovo Usiwoma
Nov 20, 2025/09:06 UTC
Greg Maxwell
Nov 20, 2025/17:23 UTC
Mat Balez
Nov 20, 2025/20:14 UTC
Jon Atack
Nov 22, 2025/15:14 UTC
Sjors Provoost
Nov 22, 2025/19:30 UTC
/dev /fd
Nov 22, 2025/20:53 UTC
Bill MacDonald
Nov 22, 2025/21:06 UTC
Murch
Nov 22, 2025/23:46 UTC
Tim Ruffing
Nov 28, 2025/15:35 UTC
Jon Atack
Nov 28, 2025/16:34 UTC
Pieter Wuille
Nov 28, 2025/19:21 UTC
Melvin Carvalho
Nov 29, 2025/23:00 UTC
Murch
Dec 2, 2025/00:29 UTC
Murch
Dec 2, 2025/22:46 UTC
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback