public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kristov Atlas <kristovatlas.lists@gmail.com>
To: Justus Ranvier <justus.ranvier@monetas.net>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] RFC: HD Bitmessage address derivation based on BIP-43
Date: Wed, 1 Jul 2015 13:07:23 -0400	[thread overview]
Message-ID: <CAGH37SJZm0qJL==aBfBGG7QsVfde-V80pnhpyPG_M0uumA+vbw@mail.gmail.com> (raw)
In-Reply-To: <CAHabJ+N3Tr5FtStH6Msmj3d8EsvjeTEV6FhSEiizLVs=5ZvCfw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 605 bytes --]

Hi Justus,

What are the potential applications for this BIP?

-Kr
On Jun 30, 2015 1:53 PM, "Justus Ranvier" <justus.ranvier@monetas.net>
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.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 1218 bytes --]

  reply	other threads:[~2015-07-01 17:07 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 [this message]
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
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='CAGH37SJZm0qJL==aBfBGG7QsVfde-V80pnhpyPG_M0uumA+vbw@mail.gmail.com' \
    --to=kristovatlas.lists@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=justus.ranvier@monetas.net \
    /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