bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-12-22 14:45:19 +00:00
Code Issues Releases Wiki Activity

Revert "BIP3: add guidance on originality, quality, LLMs"

Browse Source 
This reverts commit d083ce5a9b9d96bbbedec94a3c7878df11edd085.
This commit is contained in:
Murch 2025-12-09 14:53:26 -08:00
parent 6ce21f4eae
commit 3d07d12de5
No known key found for this signature in database
GPG Key ID: 7BA035CA5B901713
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
bip-0003.md
View File

@ -37,10 +37,7 @@ 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,
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.
documenting design decisions that have gone into implementations. BIPs may be submitted by anyone.
The scope of the BIPs
repository is limited to BIPs that do not oppose the fundamental principle that Bitcoin constitutes a peer-to-peer
@ -481,7 +478,7 @@ repository](https://github.com/bitcoin/bips) where it may get further feedback.
For each new BIP pull request that comes in, an editor checks the following:
* The idea has been previously proposed by one of the authors to the Bitcoin Development Mailing List and discussed there
* The idea has been previously discussed on the Bitcoin Development Mailing List
* The described idea is on-topic for the repository
* Title accurately describes the content
* Proposal is of general interest and/or pertains to more than one Bitcoin project/implementation
@ -490,7 +487,7 @@ For each new BIP pull request that comes in, an editor checks the following:
* Motivation, Rationale, and Backward Compatibility have been addressed
* Specification provides sufficient detail for implementation
* The defined Layer header must be correctly assigned for the given specification
* The BIP is ready: it is comprehensible, technically feasible and sound, and all aspects are addressed as necessary
* The BIP is ready: it is comprehensible, technically feasible, and all aspects are addressed as necessary
Editors do NOT evaluate whether the proposal is likely to be adopted.