Bitcoin Improvement Proposals: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
← Older edit
Luke-jr (talk | contribs)
Clerks, Administrators, Editors
3,074 edits
mNo edit summary
AllEd01 (talk | contribs)
Editors
36 edits
m spelling
 
(58 intermediate revisions by 17 users not shown)
Line 1: Line 1:
People wishing to submit BIPs, first should propose their idea or document to the mailing list. After discussion they should email Amir Taaki <genjix@riseup.net>. After copy-editing and acceptance, it will be published here.
A '''Bitcoin Improvement Proposal''' ('''BIP''') is a design document for introducing features or information to Bitcoin. This is the standard way of communicating ideas since Bitcoin has no formal structure.


We are fairly liberal with approving BIPs, and try not to be too involved in decision making on behalf of the community. The exception is in very rare cases of dispute resolution when a decision is contentious and cannot be agreed upon. In those cases, the conservative option will always be preferred.
The first BIP ([[BIP 0001]]) was submitted by Amir Taaki on 2011-08-19 and described what a BIP is.


Having a BIP here does not make it a formally accepted standard until its status becomes Active. For a BIP to become Active requires the mutual consent of the community.
== Types ==
There are three types of BIPs:
* '''Standards Track BIPs''' - Changes to the network protocol, block or transaction validation, or anything affecting interoperability.
* '''Informational BIPs''' - Design issues, general guidelines. This type of BIP is NOT for proposing new features and does not represent community consensus
* '''Process BIPs''' - Describes or proposes a change in process. Similar to Standards BIPs but apply outside the Bitcoin protocol.


Those proposing changes should consider that ultimately consent may rest with the [[economic majority]].
== Layers ==
[[BIP 0123]] established four layers for Standards BIPs:
# '''Consensus'''<ref>Further divided into [[hardfork|hard]] and [[softfork]]s.</ref>
# '''Peer Services'''
# '''API/RPC'''
# '''Applications'''


{| class="wikitable sortable" style="width: auto; text-align: center; font-size: smaller; table-layout: fixed;"
== Workflow ==
!Number
As described in [[BIP 0001]] the workflow of a BIP is as follows:
!Title
!Owner
!Status
|- style="background-color: #cfffcf"
| [[BIP 0001|1]]
| BIP Purpose and Guidelines
| Amir Taaki
| Active
|-
| [[BIP 0010|10]]
| Multi-Sig Transaction Distribution
| Alan Reiner
| Draft
|- style="background-color: #cfffcf"
| [[BIP 0011|11]]
| M-of-N Standard Transactions
| Gavin Andresen
| Accepted
|- style="background-color: #ffcfcf"
| [[BIP 0012|12]]
| OP_EVAL
| Gavin Andresen
| Withdrawn
|- style="background-color: #cfffcf"
| [[BIP 0013|13]]
| Address Format for pay-to-script-hash
| Gavin Andresen
| Accepted
|- style="background-color: #cfffcf"
| [[BIP 0014|14]]
| Protocol Version and User Agent
| Amir Taaki, Patrick Strateman
| Accepted
|- style="background-color: #ffcfcf"
| [[BIP 0015|15]]
| Aliases
| Amir Taaki
| Withdrawn
|- style="background-color: #cfffcf"
| [[BIP 0016|16]]
| Pay To Script Hash
| Gavin Andresen
| Accepted
|- style="background-color: #ffcfcf"
| [[BIP 0017|17]]
| OP_CHECKHASHVERIFY (CHV)
| Luke Dashjr
| Withdrawn
|-
| [[BIP 0018|18]]
| hashScriptCheck
| Luke Dashjr
| Draft
|-
| [[BIP 0019|19]]
| M-of-N Standard Transactions (Low SigOp)
| Luke Dashjr
| Draft
|- style="background-color: #ffcfcf"
| [[BIP 0020|20]]
| URI Scheme
| Luke Dashjr
| Replaced
|- style="background-color: #cfffcf"
| [[BIP 0021|21]]
| URI Scheme
| Nils Schneider, Matt Corallo
| Accepted
|- style="background-color: #cfffcf"
| [[BIP 0022|22]]
| getblocktemplate - Fundamentals
| Luke Dashjr
| Accepted
|-
| [[BIP 0023|23]]
| getblocktemplate - Pooled Mining
| Luke Dashjr
| Draft
|- style="background-color: #cfffcf"
| [[BIP 0030|30]]
| Duplicate transactions
| Pieter Wuille
| Accepted
|- style="background-color: #cfffcf"
| [[BIP 0031|31]]
| Pong message
| Mike Hearn
| Accepted
|-
| [[BIP 0032|32]]
| Hierarchical Deterministic Wallets
| Pieter Wuille
| Draft
|-
| [[BIP 0033|33]]
| Stratized Nodes
| Amir Taaki
| Draft
|- style="background-color: #cfffcf"
| [[BIP 0034|34]]
| Block v2, Height in coinbase
| Gavin Andresen
| Accepted
|- style="background-color: #cfffcf"
| [[BIP 0035|35]]
| mempool message
| Jeff Garzik
| Accepted
|-
| [[BIP 0036|36]]
| Custom Services
| Stefan Thomas
| Draft
|}


[[Hardfork Wishlist]]
[[File:BIP Workflow.png]]


[[Category:BIP|Z]]
== List of BIPs ==
{{BipMoved|README.mediawiki|README}}
 
== Notes ==
<references />
 
== See also ==
* [[Hardfork Wishlist]]
* [[Protocol documentation]]
* [[:Category:BIP]]
 
[[Category:BIP| ]]
 
[[es:Propuestas de mejora de Bitcoin]]

Latest revision as of 08:53, 26 September 2022

A Bitcoin Improvement Proposal (BIP) is a design document for introducing features or information to Bitcoin. This is the standard way of communicating ideas since Bitcoin has no formal structure.

The first BIP (BIP 0001) was submitted by Amir Taaki on 2011-08-19 and described what a BIP is.

Types

There are three types of BIPs:

  • Standards Track BIPs - Changes to the network protocol, block or transaction validation, or anything affecting interoperability.
  • Informational BIPs - Design issues, general guidelines. This type of BIP is NOT for proposing new features and does not represent community consensus
  • Process BIPs - Describes or proposes a change in process. Similar to Standards BIPs but apply outside the Bitcoin protocol.

Layers

BIP 0123 established four layers for Standards BIPs:

  1. Consensus[1]
  2. Peer Services
  3. API/RPC
  4. Applications

Workflow

As described in BIP 0001 the workflow of a BIP is as follows:

List of BIPs

Please do not modify this page. This is a mirror of the BIP from the source Git repository here.

Notes

  1. ↑ Further divided into hard and softforks.

See also

Retrieved from "https://en.bitcoin.it/w/index.php?title=Bitcoin_Improvement_Proposals&oldid=69461"