From: Gregory Maxwell <gmaxwell@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
Pieter Wuille <pieter.wuille@gmail.com>
Subject: Re: [Bitcoin-development] BIP 32.5
Date: Tue, 20 Aug 2013 01:35:29 -0700 [thread overview]
Message-ID: <CAAS2fgRkEFK5csXhCdArLaA_ZsFutkBBVLdHuwTn5xE-39zw3g@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQFOei6we8nfSr9DuQuHEjXT+G8_XGMk9um14DBgRuPyA@mail.gmail.com>
On Thu, Aug 15, 2013 at 7:26 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> I am wondering if we shouldn't have a BIP32 addendum which makes the
> following signing related recommendations:
Looks like we're in the midst of another DSA duplicated K disaster.
(Now, blockchain.info mywallet)
I talked to Pieter about this some earlier today and he sounded pretty
positive. I'll go ahead and start on an actual BIP document for it.
prev parent reply other threads:[~2013-08-20 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 2:26 [Bitcoin-development] BIP 32.5 Gregory Maxwell
2013-08-16 11:32 ` Mike Hearn
2013-08-16 13:29 ` Peter Todd
2013-08-16 19:37 ` Jeremy Spilman
2013-08-20 8:35 ` Gregory Maxwell [this message]
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=CAAS2fgRkEFK5csXhCdArLaA_ZsFutkBBVLdHuwTn5xE-39zw3g@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pieter.wuille@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