From: Gregory Maxwell <greg@xiph•org>
To: Erik Aronesty <erik@q32•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Addresses over Audio
Date: Fri, 12 Aug 2016 00:36:07 +0000 [thread overview]
Message-ID: <CAAS2fgTrUKvG9Eff6jNhtKfiV9v8oMDsEA9rJaViYsw50Ub5sA@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgL39qFpGAVTkNoUUR7-M2VJxqkQ=X6yK3aTsGLRAo59Jw@mail.gmail.com>
On Thu, Aug 11, 2016 at 8:37 PM, Erik Aronesty via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> Still not sure how you can take a BIP32 public seed and figure out if an
> address was derived from it though. I mean, wouldn't I have to compute all
> 2^31 possible public child addresses?
Which would take a quad core laptop about 8 hours with competent software
And presumably you're not using the whole 2^31 space else the receiver
also has to do that computation...
next prev parent reply other threads:[~2016-08-12 0:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 21:22 Daniel Hoffman
2016-08-08 22:06 ` Justin Newton
2016-08-08 22:35 ` Daniel Hoffman
2016-08-08 22:59 ` Trevin Hofmann
2016-08-09 1:50 ` Daniel Hoffman
2016-08-09 23:06 ` Daniel Hoffman
2016-08-10 0:17 ` Jannes Faber
2016-08-10 0:27 ` Chris Riley
2016-08-10 0:36 ` Luke Dashjr
2016-08-10 1:09 ` Thomas Daede
2016-08-10 1:53 ` Daniel Hoffman
2016-08-10 2:14 ` Gregory Maxwell
2016-08-10 10:41 ` Tier Nolan
2016-08-10 11:42 ` Erik Aronesty
2016-08-10 11:49 ` Theo Chino
2016-08-10 16:01 ` Daniel Hoffman
2016-08-10 17:28 ` Erik Aronesty
2016-08-10 17:38 ` Pieter Wuille
2016-08-10 17:55 ` Daniel Hoffman
2016-08-10 22:31 ` James MacWhyte
2016-08-11 13:55 ` Erik Aronesty
2016-08-11 15:13 ` Tier Nolan
2016-08-11 20:37 ` Erik Aronesty
2016-08-12 0:36 ` Gregory Maxwell [this message]
2016-08-12 12:36 ` Erik Aronesty
2016-08-12 15:49 ` Jorge Timón
2016-08-12 18:39 ` James MacWhyte
2016-08-13 4:41 ` Daniel Hoffman
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=CAAS2fgTrUKvG9Eff6jNhtKfiV9v8oMDsEA9rJaViYsw50Ub5sA@mail.gmail.com \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(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