From: Jochen Hoenicke <hoenicke@gmail•com>
To: Eric Lombrozo <elombrozo@gmail•com>,
bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Proposal to update BIP-32
Date: Fri, 22 Apr 2016 11:14:38 +0200 [thread overview]
Message-ID: <5719EB7E.5000203@gmail.com> (raw)
In-Reply-To: <CF7E1C6B-F52F-4658-AB24-553AC3493A86@gmail.com>
Am 21.04.2016 um 17:28 schrieb Eric Lombrozo:
> In practice the probability of this case triggering is on the order of
> 2^-128 or something astronomically tiny. I've been using BIP32 for a few
> years already as have many others...I don't think we've ever had to
> handle this case. Justifiably, many app developers feel like the
> additional complexity of properly handling this case is not worth the
> effort.
>
> Having said that, if the handling of this case is simple to implement
> and easy to isolate in the program flow, I am in favor of doing
> something along the lines of what you propose.
>
Yes, the idea is to handle the problem in the library so that app
developers don't have to handle the case of missing addresses or just
ignore the problem. It also doesn't add much complexity to the library
as the current implementations already test for invalid keys. The
library would then just retry instead of returning an error (that most
app developers would then ignore).
Jochen
prev parent reply other threads:[~2016-04-22 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 16:32 Jochen Hoenicke
2016-04-21 12:08 ` Marek Palatinus
2016-05-08 10:07 ` Pavol Rusnak
[not found] ` <CAAS2fgT17MQbB=Mb0qPTQcZtCY_XTeZa587w-voeeJ-WXxLagA@mail.gmail.com>
2016-05-08 11:09 ` Gregory Maxwell
[not found] ` <CAPg+sBiAv7PFWEw5s=BPcOkL-x9GfWqi24pD3xMnfxvz9xQy4g@mail.gmail.com>
2016-05-08 13:48 ` [bitcoin-dev] Fwd: " Marek Palatinus
2016-05-08 22:21 ` Pavol Rusnak
2016-04-21 15:28 ` [bitcoin-dev] " Eric Lombrozo
2016-04-21 17:23 ` Pavol Rusnak
2016-04-22 9:14 ` Jochen Hoenicke [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=5719EB7E.5000203@gmail.com \
--to=hoenicke@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=elombrozo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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