From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Fri, 4 Sep 2015 00:06:05 +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>
In-Reply-To: <CAHabJ+N3Tr5FtStH6Msmj3d8EsvjeTEV6FhSEiizLVs=5ZvCfw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201509040006.06430.luke@dashjr.org>
Cc: Justus Ranvier <justus.ranvier@monetas.net>
Subject: Re: [bitcoin-dev] RFC: HD Bitmessage address derivation based on
	BIP-43
Precedence: list

On Tuesday, June 30, 2015 5:53:05 PM Justus Ranvier wrote:
> Monetas has developed a Bitmessage address derivation method from an
> HD seed based on BIP-43.
> 
> https://github.com/monetas/bips/blob/bitmessage/bip-bm01.mediawiki
>
> We're proposing this as a BIP per the BIP-43 recommendation in order
> to reserve a purpose code.

Bitmessage is not Bitcoin, thus this falls outside the scope of the BIP 
process. 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/

Luke