public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: Justus Ranvier <justus@openbitcoinprivacyproject.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] RFC: HD Bitmessage address derivation based on BIP-43
Date: Fri, 4 Sep 2015 18:21:15 +0000	[thread overview]
Message-ID: <201509041821.16309.luke@dashjr.org> (raw)
In-Reply-To: <55E9D980.5020901@openbitcoinprivacyproject.org>

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


  reply	other threads:[~2015-09-04 18:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 17:53 [bitcoin-dev] RFC: HD Bitmessage address derivation based on BIP-43 Justus Ranvier
2015-07-01 17:07 ` Kristov Atlas
2015-07-02 15:45   ` Justus Ranvier
2015-09-04  0:06 ` Luke Dashjr
2015-09-04 17:48   ` Justus Ranvier
2015-09-04 18:21     ` Luke Dashjr [this message]
2015-09-04 18:25       ` Justus Ranvier
2015-09-05 11:17     ` Jorge Timón
2015-09-05 16:48       ` Christophe Biocca
2015-09-06  2:09         ` Jorge Timón

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201509041821.16309.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=justus@openbitcoinprivacyproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox