public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Justus Ranvier <justus@openbitcoinprivacyproject.org>
To: Luke Dashjr <luke@dashjr.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 13:25:16 -0500	[thread overview]
Message-ID: <55E9E20C.70807@openbitcoinprivacyproject.org> (raw)
In-Reply-To: <201509041821.16309.luke@dashjr.org>


[-- Attachment #1.1: Type: text/plain, Size: 622 bytes --]

On 09/04/2015 01:21 PM, Luke Dashjr wrote:
> This is not Bitcoin's problem... Polluting the BIP repository with N non-
> Bitcoin related specifications would be.

HD generation of keypairs from a single seed for many non-conflicting
uses is a valuable and useful technique.

Intentionally making a useful technology less useful because assigning
non-colliding numbers is too hard is a strange approach to software
engineering.

-- 
Justus Ranvier
Open Bitcoin Privacy Project
http://www.openbitcoinprivacyproject.org/
justus@openbitcoinprivacyproject.org
E7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623

[-- Attachment #1.2: 0xEAD9E623.asc --]
[-- Type: application/pgp-keys, Size: 18667 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2015-09-04 18:32 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
2015-09-04 18:25       ` Justus Ranvier [this message]
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=55E9E20C.70807@openbitcoinprivacyproject.org \
    --to=justus@openbitcoinprivacyproject.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=luke@dashjr.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