From: Tamas Blummer <tamas@bitsofproof.com>
To: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP32 "wallet structure" in use? Remove it?
Date: Sat, 26 Apr 2014 13:03:14 +0200 [thread overview]
Message-ID: <030D56FC-165A-4DC2-B5A2-198A4BE7F4B7@bitsofproof.com> (raw)
In-Reply-To: <FA044E89-AFCE-4E9F-B612-7DE7CBA4BB95@bitsofproof.com>
[-- Attachment #1.1: Type: text/plain, Size: 1015 bytes --]
Actually gap in parallel branches already fails with BIP64 as it starts with m/64'/…. without having m/63'
Regards,
Tamas Blummer
http://bitsofproof.com
On 26.04.2014, at 12:59, Tamas Blummer <tamas@bitsofproof.com> wrote:
> Yes, it is expensive but possible to discover any funds associated with a seed, provided there are set limits to:
>
> 1. gap of address use (e.g. 20)
> 2. depth of hierarchy (e.g. 6)
> 3. gap in use of parallel branches (e.g. 0)
>
> I would pick the limits in brackets above.
>
> Regards,
>
> Tamas Blummer
> http://bitsofproof.com
>
> On 26.04.2014, at 12:48, Tier Nolan <tier.nolan@gmail.com> wrote:
>
>> Maybe the solution is to have a defined way to import an unknown wallet?
>>
>> This means that the gap space and a search ordering needs to be defined.
>>
>> Given a blockchain and a root seed, it should be possible to find all the addresses for that root seed.
>>
>> The hierarchy that the wallet actually uses could be anything.
>
[-- Attachment #1.2: Type: text/html, Size: 7552 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2014-04-26 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 10:23 [Bitcoin-development] BIP32 "wallet structure" in use? Remove it? Andreas Schildbach
2014-04-25 14:53 ` Jim
2014-04-25 15:46 ` Gregory Maxwell
2014-04-25 15:49 ` Mike Hearn
2014-04-25 21:58 ` Aaron Voisine
2014-04-26 10:36 ` Thomas Voegtlin
2014-04-26 10:48 ` Tier Nolan
2014-04-26 10:59 ` Tamas Blummer
2014-04-26 11:03 ` Tamas Blummer [this message]
2014-04-26 12:24 ` Pavol Rusnak
2014-04-26 13:41 ` Pieter Wuille
2014-04-26 16:03 ` Jeff Garzik
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=030D56FC-165A-4DC2-B5A2-198A4BE7F4B7@bitsofproof.com \
--to=tamas@bitsofproof.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=tier.nolan@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