[Bitcoin-development] New BIP32 structure

Tamas Blummer tamas at bitsofproof.com
Wed Apr 23 18:48:22 UTC 2014

The most useful meta data to optimize chain scan is the key birth date, then the allowed gap size. 

Tamas Blummer

On 23.04.2014, at 20:39, Tier Nolan <tier.nolan at gmail.com> wrote:

> Different users could have different gap limit requirements.  20 seems very low as the default.
> A merchant could easily send 20 addresses in a row to customers and none of them bother to actually buy anything.
> Setting the gap limit to high is just a small extra cost in that case.
> Bip-32 serialization doesn't have a way of adding meta data though.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140423/88279ae3/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/20140423/88279ae3/attachment.sig>

More information about the bitcoin-dev mailing list