I will point out that the current situation is not an accident:
https://github.com/bitcoin/bips/pulls?utf8=%E2%9C%93=44 is a great
place to get some context for what happened. I believe you can also
find the other half of this discussion on the mailing list archives.
The cointypes being simple
On Sat, Sep 5, 2015 at 6:48 PM, Christophe Biocca
wrote:
> I will point out that the current situation is not an accident:
> https://github.com/bitcoin/bips/pulls?utf8=%E2%9C%93=44 is a great
> place to get some context for what happened. I believe you can also
> find
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/
>
>
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
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
The primary purpose is to allow Bitmessage users to benefit from
eternal key backups by generating their addresses from a seed.
In addition, they can use the same seed for a Bitcoin wallet and a
Bitmessage client.
This method also enables future use cases where senders calculate
Bitmessage
Hi Justus,
What are the potential applications for this BIP?
-Kr
On Jun 30, 2015 1:53 PM, Justus Ranvier justus.ranv...@monetas.net
wrote:
Monetas has developed a Bitmessage address derivation method from an
HD seed based on BIP-43.