public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet master seed with optional encryption
Date: Fri, 15 Nov 2013 19:09:07 -0800	[thread overview]
Message-ID: <BF62F0D0-1D13-4F19-A8F6-F588F3060A64@me.com> (raw)
In-Reply-To: <CAAS2fgSyegH8y1dYcijCSPLsC54mxeSNsN+3FQVDo5R9tWwAwQ@mail.gmail.com>


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


I've made no changes since the last time I've mentioned it here on the list (when the BIP procedures were being discussed).

The last changes are:

01-10-2013 - Expanded the salt to be prefix + date + checksum and renamed 'master seed' to 'root key'.
24-07-2013 - Added user selectable KDF + parameters, encoded in the prefix.
22-07-2013 - Added 2 byte creation date field, as a result, the prefix is expanded to 3 bytes.

The biggest difference between this proposal and BIP38 is that BIP38 allows a 3rd party to generate the encrypted private key + confirmation code from a passphrase code. Since this proposal is about encrypting a random value that's fed into HMAC-SHA512 and the presence of a partial hash of the root address, that's not possible.




>> https://bitcointalk.org/index.php?topic=258678
> 
> Greetings.  Any recent progress on this?
> 
> Do we believe this proposal can replace BIP38?  If not, what are the
> limitations that would prevent it from doing so?


[-- Attachment #1.2: Type: text/html, Size: 1590 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

  reply	other threads:[~2013-11-16  3:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <op.w0hd2nthyldrnw@laptop-air>
2013-07-19 18:15 ` [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet master seed with optional encryption Jean-Paul Kogelman
2013-07-22 13:14   ` Mike Hearn
2013-07-22 14:33     ` Jean-Paul Kogelman
2013-07-22 21:37     ` Jean-Paul Kogelman
2013-11-16  2:47       ` Gregory Maxwell
2013-11-16  3:09         ` Jean-Paul Kogelman [this message]
2013-12-26 11:48           ` Jean-Paul Kogelman
2014-03-12  3:17             ` [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet root key " Jean-Paul Kogelman
2014-03-12 13:11               ` Pavol Rusnak
2014-03-12 15:45                 ` Jean-Paul Kogelman
2014-03-12 15:55                   ` Pavol Rusnak
2014-03-12 16:49                     ` Gary Rowe
2014-03-12 18:00                       ` William Yager
2014-03-12 19:35                       ` Jean-Paul Kogelman
2014-03-12 19:41                         ` Gary Rowe
2014-03-12 19:26                     ` Jean-Paul Kogelman
2014-03-12 19:39                       ` Pavol Rusnak
2014-03-12 19:55                         ` William Yager
2014-03-12 20:04                           ` Pavol Rusnak
2014-03-12 20:10                             ` William Yager
2014-03-12 20:24                               ` Pavol Rusnak
2014-03-12 20:37                                 ` William Yager
2014-03-12 20:42                                   ` Pavol Rusnak
2014-03-12 20:49                                     ` William Yager
2014-03-12 21:08                                 ` Jean-Paul Kogelman
2014-03-12 21:15                                   ` William Yager
     [not found] <CAFmyj8wDQ7p080QHFPkhfCXttCUPfrLxKqzo_2zgyTJVk9OTZg@mail.gmail.com>
2013-07-19 18:11 ` [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet master seed " Jean-Paul Kogelman
2013-07-19 17:46 Jean-Paul Kogelman

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=BF62F0D0-1D13-4F19-A8F6-F588F3060A64@me.com \
    --to=jeanpaulkogelman@me.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gmaxwell@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