From: Justus Ranvier <justus.ranvier@monetas.net>
To: Kristov Atlas <kristovatlas.lists@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] RFC: HD Bitmessage address derivation based on BIP-43
Date: Thu, 2 Jul 2015 10:45:05 -0500 [thread overview]
Message-ID: <CAHabJ+NLVSsgu5k6aGRwTSFybp-K0h+=5v0=8+=eicrt1NLj7Q@mail.gmail.com> (raw)
In-Reply-To: <CAGH37SJZm0qJL==aBfBGG7QsVfde-V80pnhpyPG_M0uumA+vbw@mail.gmail.com>
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 addresses based on a recipient's extended public key and
some other index value.
On Wed, Jul 1, 2015 at 12:07 PM, Kristov Atlas
<kristovatlas.lists@gmail.com> wrote:
> 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
next prev parent reply other threads:[~2015-07-02 15:45 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 [this message]
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='CAHabJ+NLVSsgu5k6aGRwTSFybp-K0h+=5v0=8+=eicrt1NLj7Q@mail.gmail.com' \
--to=justus.ranvier@monetas.net \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=kristovatlas.lists@gmail.com \
/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