rich1.0npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8https://nostr.ae/npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8njumphttps://nostr.ae📅 Original date posted:2014-04-23 📝 Original message:The most useful meta data to optimize chain scan is the key birth date, then the allowed gap size. Tamas Blummer http://bitsofproof.com 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>