BIP 0002 - Revision history

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/7bd6c2c500cd5e8c/bip-0002.mediawiki

2024-04-24T20:07:49Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/7bd6c2c500cd5e8c/bip-0002.mediawiki

← Older revision		Revision as of 20:07, 24 April 2024
Line 105:		Line 105:

	The BIP editors are intended to fulfill administrative and editorial responsibilities. The BIP editors monitor BIP changes, and update BIP headers as appropriate.		The BIP editors are intended to fulfill administrative and editorial responsibilities. The BIP editors monitor BIP changes, and update BIP headers as appropriate.

			BIP editors may also, at their option, unilaterally make and merge strictly-editorial changes to BIPs, such as correcting misspellings, fixing broken links, etc.

	==BIP format and structure==		==BIP format and structure==

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/f450bee7a4efeff2/bip-0002.mediawiki

2024-04-23T18:35:34Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/f450bee7a4efeff2/bip-0002.mediawiki

← Older revision		Revision as of 18:35, 23 April 2024
Line 71:		Line 71:
	The current BIP editors are:		The current BIP editors are:

			* Bryan Bishop ([[mailto:kanzure@gmail.com\|kanzure@gmail.com]])
			* Jon Atack ([[mailto:jon@atack.com\|jon@atack.com]])
	* Luke Dashjr ([[mailto:luke_bipeditor@dashjr.org\|luke_bipeditor@dashjr.org]])		* Luke Dashjr ([[mailto:luke_bipeditor@dashjr.org\|luke_bipeditor@dashjr.org]])
	* ~~Kalle Alm~~ ([[mailto:~~karljohan-alm~~@~~garage~~.co.jp\|~~karljohan-alm~~@~~garage~~.co.jp]])		* Mark "Murch" Erhardt ([[mailto:murch@murch.one\|murch@murch.one]])
			* Olaoluwa Osuntokun ([[mailto:laolu32@gmail.com\|laolu32@gmail.com]])
			* Ruben Somsen ([[mailto:rsomsen@gmail.com\|rsomsen@gmail.com]])

	===BIP Editor Responsibilities & Workflow===		===BIP Editor Responsibilities & Workflow===

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/57c3d4a0d71c9ca1/bip-0002.mediawiki

2024-04-22T18:38:26Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/57c3d4a0d71c9ca1/bip-0002.mediawiki

← Older revision		Revision as of 18:38, 22 April 2024
Line 36:		Line 36:
	Additionally, many ideas have been brought forward for changing Bitcoin that have been rejected for various reasons.		Additionally, many ideas have been brought forward for changing Bitcoin that have been rejected for various reasons.
	The first step should be to search past discussions to see if an idea has been considered before, and if so, what issues arose in its progression.		The first step should be to search past discussions to see if an idea has been considered before, and if so, what issues arose in its progression.
	After investigating past work, the best way to proceed is by posting about the new idea to the [https://~~lists~~.~~linuxfoundation~~.~~org~~/~~mailman~~/~~listinfo/bitcoin-dev~~ Bitcoin development mailing list].		After investigating past work, the best way to proceed is by posting about the new idea to the [https://groups.google.com/g/bitcoindev Bitcoin development mailing list].

	Vetting an idea publicly before going as far as writing a BIP is meant to save both the potential author and the wider community time.		Vetting an idea publicly before going as far as writing a BIP is meant to save both the potential author and the wider community time.
Line 42:		Line 42:
	It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Bitcoin is used.		It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Bitcoin is used.

	Once the champion has asked the Bitcoin community as to whether an idea has any chance of acceptance, a draft BIP should be presented to the [https://~~lists~~.~~linuxfoundation~~.~~org~~/~~mailman~~/~~listinfo/bitcoin-dev~~ Bitcoin development mailing list].		Once the champion has asked the Bitcoin community as to whether an idea has any chance of acceptance, a draft BIP should be presented to the [https://groups.google.com/g/bitcoindev Bitcoin development mailing list].
	This gives the author a chance to flesh out the draft BIP to make it properly formatted, of high quality, and to address additional concerns about the proposal.		This gives the author a chance to flesh out the draft BIP to make it properly formatted, of high quality, and to address additional concerns about the proposal.
	Following a discussion, the proposal should be submitted to the [https://github.com/bitcoin/bips BIPs git repository] as a pull request.		Following a discussion, the proposal should be submitted to the [https://github.com/bitcoin/bips BIPs git repository] as a pull request.

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/c66583158b9cde82/bip-0002.mediawiki

2024-04-22T17:08:45Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/c66583158b9cde82/bip-0002.mediawiki

← Older revision		Revision as of 17:08, 22 April 2024
Line 413:		Line 413:
	* Email addresses are now required for authors.		* Email addresses are now required for authors.
	* The Post-History header may be provided as a link instead of a simple date.		* The Post-History header may be provided as a link instead of a simple date.
	* Markdown format is no longer permitted for BIPs.
	* The Resolution header has been dropped, as it is not applicable to a decentralised system where no authority exists to make final decisions.		* The Resolution header has been dropped, as it is not applicable to a decentralised system where no authority exists to make final decisions.

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/9c57fac1a71d20f6/bip-0002.mediawiki

2023-12-18T06:34:46Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/9c57fac1a71d20f6/bip-0002.mediawiki

← Older revision		Revision as of 06:34, 18 December 2023
Line 106:		Line 106:
	===Specification===		===Specification===

	BIPs should be written in mediawiki format.		BIPs should be written in mediawiki or markdown format.

	Each BIP should have the following parts:		Each BIP should have the following parts:

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/edffe529056f6dfd/bip-0002.mediawiki

2021-12-15T15:41:53Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/edffe529056f6dfd/bip-0002.mediawiki

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0002.mediawiki

2019-09-24T17:58:37Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0002.mediawiki

Show changes

JonathanCross: Updating Preamble

2017-05-14T17:35:03Z

Updating Preamble

← Older revision		Revision as of 17:35, 14 May 2017
Line 3:		Line 3:
	<pre>		<pre>
	BIP: 2		BIP: 2
	Title: BIP ~~Status and Comments~~		Title: BIP process, revised
	Author: Luke Dashjr <luke+bip@dashjr.org>		Author: Luke Dashjr <luke+bip@dashjr.org>
	Status: ~~Draft~~		Comments-Summary: No comments yet.
			Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0002
			Status: Active
	Type: Process		Type: Process
	Created: 2016-02-03		Created: 2016-02-03
			License: BSD-2-Clause
			OPL
			Replaces: 1
	</pre>		</pre>

Spaz926 at 02:31, 12 February 2016

2016-02-12T02:31:35Z

← Older revision		Revision as of 02:31, 12 February 2016
Line 10:		Line 10:
	</pre>		</pre>

	{{BipMoved\|bip-~~0010~~.mediawiki}}		{{BipMoved\|bip-0002.mediawiki}}

	[[Category:BIP\|D]]		[[Category:BIP\|D]]

Spaz926: Created page with "{{bip}}

   BIP: 2   Title: BIP Status and Comments   Author: Luke Dashjr    Status: Draft   Type: Process   Created: 2016-02-03

{{BipMoved|b..."

2016-02-12T02:28:56Z

Created page with "{{bip}} <pre> BIP: 2 Title: BIP Status and Comments Author: Luke Dashjr <luke+bip@dashjr.org> Status: Draft Type: Process Created: 2016-02-03 </pre> {{BipMoved|b..."

New page

{{bip}}

<pre>
BIP: 2
Title: BIP Status and Comments
Author: Luke Dashjr <luke+bip@dashjr.org>
Status: Draft
Type: Process
Created: 2016-02-03
</pre>

{{BipMoved|bip-0010.mediawiki}}

[[Category:BIP|D]]

← Older revision		Revision as of 15:41, 15 December 2021
Line 45:		Line 45:
	This gives the author a chance to flesh out the draft BIP to make it properly formatted, of high quality, and to address additional concerns about the proposal.		This gives the author a chance to flesh out the draft BIP to make it properly formatted, of high quality, and to address additional concerns about the proposal.
	Following a discussion, the proposal should be submitted to the [https://github.com/bitcoin/bips BIPs git repository] as a pull request.		Following a discussion, the proposal should be submitted to the [https://github.com/bitcoin/bips BIPs git repository] as a pull request.
	This draft must be written in BIP style as described below, and named with an alias such as "bip-johndoe-infinitebitcoins" until ~~the~~ editor has assigned it a BIP number (authors MUST NOT self-assign BIP numbers).		This draft must be written in BIP style as described below, and named with an alias such as "bip-johndoe-infinitebitcoins" until an editor has assigned it a BIP number (authors MUST NOT self-assign BIP numbers).

	BIP authors are responsible for collecting community feedback on both the initial idea and the BIP before submitting it for review. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. Strategies to keep the discussions efficient include: setting up a separate SIG mailing list for the topic, having the BIP author accept private comments in the early design phases, setting up a wiki page or git repository, etc. BIP authors should use their discretion here.		BIP authors are responsible for collecting community feedback on both the initial idea and the BIP before submitting it for review. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. Strategies to keep the discussions efficient include: setting up a separate SIG mailing list for the topic, having the BIP author accept private comments in the early design phases, setting up a wiki page or git repository, etc. BIP authors should use their discretion here.
Line 51:		Line 51:
	It is highly recommended that a single BIP contain a single key proposal or new idea. The more focused the BIP, the more successful it tends to be. If in doubt, split your BIP into several well-focused ones.		It is highly recommended that a single BIP contain a single key proposal or new idea. The more focused the BIP, the more successful it tends to be. If in doubt, split your BIP into several well-focused ones.

	When the BIP draft is complete, ~~the~~ BIP editor will assign the BIP a number, label it as Standards Track, Informational, or Process, and merge the pull request to the BIPs git repository.		When the BIP draft is complete, a BIP editor will assign the BIP a number, label it as Standards Track, Informational, or Process, and merge the pull request to the BIPs git repository.
	The BIP ~~editor~~ will not unreasonably reject a BIP.		The BIP editors will not unreasonably reject a BIP.
	Reasons for rejecting BIPs include duplication of effort, disregard for formatting rules, being too unfocused or too broad, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Bitcoin philosophy.		Reasons for rejecting BIPs include duplication of effort, disregard for formatting rules, being too unfocused or too broad, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Bitcoin philosophy.
	For a BIP to be accepted it must meet certain minimum criteria.		For a BIP to be accepted it must meet certain minimum criteria.
Line 65:		Line 65:
	It occasionally becomes necessary to transfer ownership of BIPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred BIP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the BIP process, or has fallen off the face of the 'net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the BIP. We try to build consensus around a BIP, but if that's not possible, you can always submit a competing BIP.		It occasionally becomes necessary to transfer ownership of BIPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred BIP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the BIP process, or has fallen off the face of the 'net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the BIP. We try to build consensus around a BIP, but if that's not possible, you can always submit a competing BIP.

	If you are interested in assuming ownership of a BIP, send a message asking to take over, addressed to both the original author and the BIP ~~editor~~. If the original author doesn't respond to email in a timely manner, the BIP ~~editor~~ will make a unilateral decision (it's not like such decisions can't be reversed :).		If you are interested in assuming ownership of a BIP, send a message asking to take over, addressed to both the original author and the BIP editors. If the original author doesn't respond to email in a timely manner, the BIP editors will make a unilateral decision (it's not like such decisions can't be reversed :).

	===BIP Editors===		===BIP Editors===

	The current BIP ~~editor is~~ Luke Dashjr ~~who can be contacted at~~ [[mailto:luke_bipeditor@dashjr.org\|luke_bipeditor@dashjr.org]].		The current BIP editors are:

			* Luke Dashjr ([[mailto:luke_bipeditor@dashjr.org\|luke_bipeditor@dashjr.org]])
			* Kalle Alm ([[mailto:karljohan-alm@garage.co.jp\|karljohan-alm@garage.co.jp]])

	===BIP Editor Responsibilities & Workflow===		===BIP Editor Responsibilities & Workflow===

	The BIP ~~editor subscribes~~ to the Bitcoin development mailing list.		The BIP editors subscribe to the Bitcoin development mailing list.
	Off-list BIP-related correspondence should be sent (or CC'd) to ~~luke_bipeditor@dashjr.org~~.		Off-list BIP-related correspondence should be sent (or CC'd) to the BIP editors.

	For each new BIP that comes in an editor does the following:		For each new BIP that comes in an editor does the following:
Line 190:		Line 193:

	Champions of a BIP may decide on their own to change the status between Draft, Deferred, or Withdrawn.		Champions of a BIP may decide on their own to change the status between Draft, Deferred, or Withdrawn.
	~~The~~ BIP editor may also change the status to Deferred when no progress is being made on the BIP.		A BIP editor may also change the status to Deferred when no progress is being made on the BIP.

	A BIP may only change status from Draft (or Rejected) to Proposed, when the author deems it is complete, has a working implementation (where applicable), and has community plans to progress it to the Final status.		A BIP may only change status from Draft (or Rejected) to Proposed, when the author deems it is complete, has a working implementation (where applicable), and has community plans to progress it to the Final status.
Line 196:		Line 199:
	BIPs should be changed from Draft or Proposed status, to Rejected status, upon request by any person, if they have not made progress in three years. Such a BIP may be changed to Draft status if the champion provides revisions that meaningfully address public criticism of the proposal, or to Proposed status if it meets the criteria required as described in the previous paragraph.		BIPs should be changed from Draft or Proposed status, to Rejected status, upon request by any person, if they have not made progress in three years. Such a BIP may be changed to Draft status if the champion provides revisions that meaningfully address public criticism of the proposal, or to Proposed status if it meets the criteria required as described in the previous paragraph.

	An Proposed BIP may progress to Final only when specific criteria reflecting real-world adoption has occurred. This is different for each BIP depending on the nature of its proposed changes, which will be expanded on below. Evaluation of this status change should be objectively verifiable, and/or be discussed on the development mailing list.		A Proposed BIP may progress to Final only when specific criteria reflecting real-world adoption has occurred. This is different for each BIP depending on the nature of its proposed changes, which will be expanded on below. Evaluation of this status change should be objectively verifiable, and/or be discussed on the development mailing list.

	When a Final BIP is no longer relevant, its status may be changed to Replaced or Obsolete (which is equivalent to Replaced). This change must also be objectively verifiable and/or discussed.		When a Final BIP is no longer relevant, its status may be changed to Replaced or Obsolete (which is equivalent to Replaced). This change must also be objectively verifiable and/or discussed.
Line 330:		Line 333:
	In this case, the BIP text is fully licensed under both the OSI-approved BSD 2-clause license as well as the GNU All-Permissive License, and anyone may modify and redistribute the text provided they comply with the terms of either license. In other words, the license list is an "OR choice", not an "AND also" requirement.		In this case, the BIP text is fully licensed under both the OSI-approved BSD 2-clause license as well as the GNU All-Permissive License, and anyone may modify and redistribute the text provided they comply with the terms of either license. In other words, the license list is an "OR choice", not an "AND also" requirement.

	It is also possible to license source code differently from the BIP text. A optional License-Code header is placed after the License header. Again, each license must be referenced by their respective abbreviation given below.		It is also possible to license source code differently from the BIP text. An optional License-Code header is placed after the License header. Again, each license must be referenced by their respective abbreviation given below.

	For example, a preamble specifying the optional License-Code header might look like:		For example, a preamble specifying the optional License-Code header might look like: