From 23d3417fb410835e2aa83dc673c4ff7f04b615c0 Mon Sep 17 00:00:00 2001 From: Luke Dashjr Date: Sat, 15 Nov 2025 20:35:53 +0000 Subject: [PATCH] bip-0003: Clarify the need for relevance as a standard --- bip-0003.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/bip-0003.md b/bip-0003.md index b1d4440a..54aad840 100644 --- a/bip-0003.md +++ b/bip-0003.md @@ -37,7 +37,9 @@ Some BIPs describe processes, implementation guidelines, best practices, inciden the Bitcoin protocol, peer-to-peer network, and client software may be acceptable. BIPs are intended to be a means for proposing new protocol features, coordinating client standards, and -documenting design decisions that have gone into implementations. A BIP may be submitted by anyone, +documenting design decisions that have gone into implementations thereof. +BIPs should cover topics that at least potentially have a need of standardization, involving multiple projects, and not merely configuration (such as default settings or per-node policies, except where the latter may overlap with standardized interactions). +A BIP may be submitted by anyone, provided it is the original work of its authors and the content is of high quality, e.g. does not waste the community's time. No content may be generated by AI/LLMs and authors must proactively disclose up-front any use of AI/LLMs.