BIP 3 and issues on BIPs

Posted by Anthony Towns

May 27, 2026/01:51 UTC

The discussion around Bitcoin Improvement Proposals (BIPs) has highlighted some concerns regarding the current feedback mechanisms as outlined in BIP 3. The critique emphasizes that the lack of a centralized location for previous discussions and feedback about BIPs complicates the process of reviewing historical inputs. Contributors must resort to searching through various platforms such as bitcoin-dev mailing lists, Stacker.news, Twitter, Nostr, and other random blogs to find relevant discussions, which is less than ideal.

There is a suggestion to categorize feedback into three distinct classes to streamline this process. The first class includes concerns acknowledged by BIP authors but not yet addressed. It has been proposed that these could be added directly to the affected BIP under a new section titled "Unresolved Issues," provided there is consensus among the authors. This addition would clearly highlight outstanding issues without halting the progress of the BIP unless it remains unresolved.

The second class of feedback pertains to issues where there is a general agreement on the concern's validity among the BIP editors, despite the authors' objections. For this type of feedback, establishing a dedicated feedback document within the BIP repository might be beneficial. Such a document could serve as a collective repository for similar concerns across different BIPs, managed and periodically reviewed by the BIP editors to decide its relevance and visibility.

Lastly, the third class involves feedback generally disregarded as irrelevant or trolling, which would continue to be excluded from the formal BIP discussion channels and left to be raised through external mediums like personal blogs or social media.

Implementing these changes could significantly improve how feedback is handled and integrated into the ongoing development and refinement of BIPs. By structuring feedback more effectively, the community can ensure that all valid concerns are appropriately considered without overwhelming the documentation with every single piece of feedback received. This structured approach could enhance clarity and focus during the development phases of future BIPs.

Link to Raw Post
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