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
|
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 F2C02105A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 18:21:26 +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 8A021106
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 18:21:26 +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 7D7CB10801BA;
Fri, 4 Sep 2015 18:21:17 +0000 (UTC)
X-Hashcash: 1:25:150904:justus@openbitcoinprivacyproject.org::y8QdGNjrqlMU0CiF:l4iL
X-Hashcash: 1:25:150904:bitcoin-dev@lists.linuxfoundation.org::ez=hkganqs2VL829:BGqQ
From: Luke Dashjr <luke@dashjr.org>
To: Justus Ranvier <justus@openbitcoinprivacyproject.org>
Date: Fri, 4 Sep 2015 18:21:15 +0000
User-Agent: KMail/1.13.7 (Linux/4.1.1-gentoo-r1; KDE/4.14.8; x86_64; ; )
References: <CAHabJ+N3Tr5FtStH6Msmj3d8EsvjeTEV6FhSEiizLVs=5ZvCfw@mail.gmail.com>
<201509040006.06430.luke@dashjr.org>
<55E9D980.5020901@openbitcoinprivacyproject.org>
In-Reply-To: <55E9D980.5020901@openbitcoinprivacyproject.org>
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="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201509041821.16309.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
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] RFC: HD Bitmessage address derivation based on
BIP-43
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: Fri, 04 Sep 2015 18:21:27 -0000
On Friday, September 04, 2015 5:48:48 PM Justus Ranvier wrote:
> On 09/03/2015 07:06 PM, Luke Dashjr via bitcoin-dev wrote:
> > Since BIP 43 is still a draft, I propose modifying it to refer non-
> >
> > Bitcoin purpose codes to the SLIP repository:
> > https://doc.satoshilabs.com/slips/
>
> What benefit is created by delegating the BIP-43 namespace management to
> that company in particular?
Feel free to create a company-independent repository instead.
Although I don't think SLIPs are intended to be biased toward their company.
> BIP-43 as it is currently composed provides the convenient feature of
> purpose codes matching the BIP number. Moving purpose codes to a
> separate namespace add complexity to its usage for no discernible benefit.
This is not Bitcoin's problem... Polluting the BIP repository with N non-
Bitcoin related specifications would be.
Luke
|