[Bitcoin-development] BIP32 "wallet structure" in use? Remove it?

Tamas Blummer tamas at bitsofproof.com
Sat Apr 26 11:03:14 UTC 2014

Actually gap in parallel branches already fails with BIP64 as it starts with m/64'/…. without having m/63'


Tamas Blummer

On 26.04.2014, at 12:59, Tamas Blummer <tamas at 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 at 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/16c43082/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/16c43082/attachment.sig>

More information about the bitcoin-dev mailing list