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
80
81
82
83
84
85
86
87
|
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 7EEDB71
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 23 Aug 2016 20:12:29 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from zinan.dashjr.org (unknown [192.3.11.21])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 341F4FD
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 23 Aug 2016 20:12:29 +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 1D40738AB6EA
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 23 Aug 2016 20:12:14 +0000 (UTC)
X-Hashcash: 1:25:160823:bitcoin-dev@lists.linuxfoundation.org::AqyF6xIKHowcQY4h:bspLM
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Tue, 23 Aug 2016 20:12:11 +0000
User-Agent: KMail/1.13.7 (Linux/4.1.18-gentoo; KDE/4.14.20; 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
X-PRIORITY: 2 (High)
Priority: urgent
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201608232012.12588.luke@dashjr.org>
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,RDNS_DYNAMIC
autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: [bitcoin-dev] BIP Status updates (including to Active/Final Status)
- BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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, 23 Aug 2016 20:12:29 -0000
A number of BIPs seem ready for updating to Final Status. If there are no
objections, I will update these in 2 weeks:
BIP 39: Mnemonic code for generating deterministic keys
- Used by many wallets and hundreds of thousands of users.
BIP 44: Multi-Account Hierarchy for Deterministic Wallets
- Appears to be implemented by multiple wallets.
BIP 67: Deterministic Pay-to-script-hash multi-signature addresses through
public key sorting
- Implementations in multiple wallet software exist.
BIP 125: Opt-in Full Replace-by-Fee Signaling
- Implemented in Bitcoin Core and derivatives; appears to be in regular use on
the network.
BIP 130: sendheaders message
- Implemented in Bitcoin Core and derivatives.
Also, BIP 43 (Purpose Field for Deterministic Wallets) is an informational BIP
which appears to be guiding to some extent the creation of new BIPs; therefore
I propose its Status be upgraded to Active. I will make this update in 2 weeks
also, if no objections.
Additionally, BIP 111 (NODE_BLOOM service bit) has been implemented in Bitcoin
Core and derivatives; it is unclear if used by clients yet. Can developers of
such clients please comment and let me know: 1) if their software supports
this BIP already; 2) if not, do they intend to support it in the future?
If and only if there are any clients using this service bit already, I will
update BIP 111 to Final Status in 2 weeks also.
Thanks,
Luke
|
