BIP 0014 - Revision history

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

2024-04-30T21:50:49Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/51b2d131bea737bc/bip-0014.mediawiki

← Older revision		Revision as of 21:50, 30 April 2024
Line 32:		Line 32:
	By using a protocol version, we set all implementations on the network to a common standard. Everybody is able to agree within their confines what is protocol and what is implementation-dependent. A user agent string is offered as a 'vanity-plate' for clients to distinguish themselves in the network.		By using a protocol version, we set all implementations on the network to a common standard. Everybody is able to agree within their confines what is protocol and what is implementation-dependent. A user agent string is offered as a 'vanity-plate' for clients to distinguish themselves in the network.

	Separation of the network protocol from the ~~implemention~~, and forming development of said protocol by means of a mutual consensus among participants, has the democratic disadvantage when agreement is hard to reach on contentious issues. To mitigate this issue, strong communication channels and fast release schedules are needed, and are outside the scope of this document (concerning a process-BIP type).		Separation of the network protocol from the implementation, and forming development of said protocol by means of a mutual consensus among participants, has the democratic disadvantage when agreement is hard to reach on contentious issues. To mitigate this issue, strong communication channels and fast release schedules are needed, and are outside the scope of this document (concerning a process-BIP type).

	User agents provide extra tracking information that is useful for keeping tabs on network data such as client implementations used or common architectures/operating-systems. In the rare case they may even provide an emergency method of shunning faulty clients that threaten network health- although this is strongly unrecommended and extremely bad form. The user agent does not provide a method for clients to work around and behave differently to different implementations, as this will lead to protocol fracturing.		User agents provide extra tracking information that is useful for keeping tabs on network data such as client implementations used or common architectures/operating-systems. In the rare case they may even provide an emergency method of shunning faulty clients that threaten network health- although this is strongly unrecommended and extremely bad form. The user agent does not provide a method for clients to work around and behave differently to different implementations, as this will lead to protocol fracturing.

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

2019-09-24T18:00:57Z

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

@@ Line 1: / Line 1: @@
 {{bip}}
 <pre>
    BIP: 14
-   Title: BIP Protocol Version and User Agent
+  Layer: Peer Services
    Author: Amir Taaki <genjix@riseup.net>
            Patrick Strateman <bitcoin-bips@covertinferno.org>
-   Status: Accepted
+  Comments-Summary: No comments yet.
    Type: Standards Track
-   Created: 10-11-2011
+   Created: 2011-11-10
-   Post-History: 02-11-2011
+   Post-History: 2011-11-02
 </pre>
-{{BipMoved|bip-0014.mediawiki}}
+In this document, bitcoin will be used to refer to the protocol while Satoshi will refer to the current client in order to prevent confusion.
-[[Category:BIP|C]]
+When this document was published, the bitcoin protocol and Satoshi client versions were currently at 0.5 and undergoing changes. In order to minimise disruption and allow the undergoing changes to be completed, the next protocol version at 0.6 became peeled from the client version (also at 0.6). As of that time (January 2012), protocol and implementation version numbers are distinct from each other.

934: Removing redundant parameter.

2015-12-29T13:43:41Z

Removing redundant parameter.

← Older revision		Revision as of 13:43, 29 December 2015
Line 12:		Line 12:
	</pre>		</pre>

	{{BipMoved\|bip-0014.mediawiki~~\|BIP 0014~~}}		{{BipMoved\|bip-0014.mediawiki}}

	[[Category:BIP\|C]]		[[Category:BIP\|C]]

Wumpus: Github move

2013-12-06T07:41:18Z

Github move

@@ Line 12: / Line 12: @@
 </pre>
-In this document, bitcoin will be used to refer to the protocol while Satoshi will refer to the current client in order to prevent confusion.
+{{BipMoved|bip-0014.mediawiki|BIP 0014}}
 [[Category:BIP|C]]

Nanotube: Removed protection from "BIP 0014"

2013-01-18T14:58:02Z

Removed protection from "BIP 0014"

← Older revision	Revision as of 14:58, 18 January 2013
(No difference)

Genjix at 17:12, 16 April 2012

2012-04-16T17:12:11Z

← Older revision		Revision as of 17:12, 16 April 2012
Line 1:		Line 1:
			{{bip}}

	<pre>		<pre>
	BIP: 14		BIP: 14

Genjix: Protected "BIP 0014": submit bips to genjix ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2012-01-31T21:38:41Z

Protected "BIP 0014": submit bips to genjix ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 21:38, 31 January 2012
(No difference)

Giszmo: Added to category BIP

2012-01-29T18:27:26Z

Added to category BIP

← Older revision		Revision as of 18:27, 29 January 2012
Line 89:		Line 89:
	When this document was published, the bitcoin protocol and Satoshi client versions were currently at 0.5 and undergoing changes. In order to minimise disruption and allow the undergoing changes to be completed, the next protocol version at 0.6 became peeled from the client version (also at 0.6). As of that time (January 2012), protocol and implementation version numbers are distinct from each other.		When this document was published, the bitcoin protocol and Satoshi client versions were currently at 0.5 and undergoing changes. In order to minimise disruption and allow the undergoing changes to be completed, the next protocol version at 0.6 became peeled from the client version (also at 0.6). As of that time (January 2012), protocol and implementation version numbers are distinct from each other.

	[[Category:BIP]]		[[Category:BIP\|C]]

Giszmo: Added to category BIP

2012-01-29T18:15:32Z

Added to category BIP

← Older revision		Revision as of 18:15, 29 January 2012
Line 88:		Line 88:

	When this document was published, the bitcoin protocol and Satoshi client versions were currently at 0.5 and undergoing changes. In order to minimise disruption and allow the undergoing changes to be completed, the next protocol version at 0.6 became peeled from the client version (also at 0.6). As of that time (January 2012), protocol and implementation version numbers are distinct from each other.		When this document was published, the bitcoin protocol and Satoshi client versions were currently at 0.5 and undergoing changes. In order to minimise disruption and allow the undergoing changes to be completed, the next protocol version at 0.6 became peeled from the client version (also at 0.6). As of that time (January 2012), protocol and implementation version numbers are distinct from each other.

			[[Category:BIP]]

Genjix at 17:21, 13 December 2011

2011-12-13T17:21:17Z

← Older revision		Revision as of 17:21, 13 December 2011
Line 4:		Line 4:
	Author: Amir Taaki <genjix@riseup.net>		Author: Amir Taaki <genjix@riseup.net>
	Patrick Strateman <bitcoin-bips@covertinferno.org>		Patrick Strateman <bitcoin-bips@covertinferno.org>
	Status: ~~Draft~~		Status: Accepted
	Type: Standards Track		Type: Standards Track
	Created: 10-11-2011		Created: 10-11-2011