summaryrefslogtreecommitdiff
path: root/69/5cb482027e0c95b1845e7d4cb37c3c72567f6e
blob: e0e8f4aa829f216d10e4882ba0f6b826d3d51f7f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Return-Path: <luke@dashjr.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 8B839DE7
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  8 Mar 2016 19:04:32 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id 0BAC4109
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  8 Mar 2016 19:04:31 +0000 (UTC)
Received: from ishibashi.localnet (unknown
	[IPv6:2001:470:5:265:61b6:56a6:b03d:28d6])
	(Authenticated sender: luke-jr)
	by zinan.dashjr.org (Postfix) with ESMTPSA id 9788038A2C8F
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  8 Mar 2016 19:04:29 +0000 (UTC)
X-Hashcash: 1:25:160308:bitcoin-dev@lists.linuxfoundation.org::JFlhBTvyUV7eejdZ:ojPi
From: Luke Dashjr <luke@dashjr.org>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Date: Tue, 8 Mar 2016 19:04:27 +0000
User-Agent: KMail/1.13.7 (Linux/4.1.18-gentoo; KDE/4.14.8; x86_64; ; )
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201603081904.28687.luke@dashjr.org>
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 08 Mar 2016 19:10:34 +0000
Subject: [bitcoin-dev] BIP 2 promotion to Final
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2016 19:04:32 -0000
X-List-Received-Date: Tue, 08 Mar 2016 19:04:32 -0000

It has been about 1 month since BIP 2 finished receiving comments, so I 
believe it is an appropriate time to begin the process of moving it to Final 
Status. Toward this end, I have opened a pull request:

    https://github.com/bitcoin/bips/pull/350

The current requirement for this is that "the reference implementation is 
complete and accepted by the community". Given the vagueness of this criteria, 
I intend to move forward applying BIP 2's more specific criteria to itself:

> A process BIP may change status from Draft to Active when it achieves rough
> consensus on the mailing list. Such a proposal is said to have rough
> consensus if it has been open to discussion on the development mailing list
> for at least one month, and no person maintains any unaddressed
> substantiated objections to it. Addressed or obstructive objections may be
> ignored/overruled by general agreement that they have been sufficiently
> addressed, but clear reasoning must be given in such circumstances.

Furthermore, there is a reference implementation in the mentioned PR.

Please review the latest draft BIP and provide any objections ASAP.
If there are no outstanding objections on 2016 April 9th, I will consider the 
current draft to have reached rough consensus and update its Status to Final 
by merging the PR.

Thanks,

Luke