Jochen Hoenicke [ARCHIVE] on Nostr: 📅 Original date posted:2016-08-24 📝 Original message:On 24.08.2016 16:18, Jonas ...
📅 Original date posted:2016-08-24
📝 Original message:On 24.08.2016 16:18, Jonas Schnelli via bitcoin-dev wrote:
>
> Another thing that I think could be a BIP misdesign:
>
> BIP44 Gap Limits
> From the BIP:
>
> ----------
> "Address gap limit is currently set to 20. If the software hits 20
> unused addresses in a row, it expects there are no used addresses beyond
> this point and stops searching the address chain."
> ----------
>
> * Does that mean, we do a transaction rescan back to the genesis block
> for every 20 addresses?
As I understand it, you can scan sequentially starting with the genesis
block (or with a block at around the time when BIP44 was written). Then
if you find a new transaction, which requires to generate new addresses,
you generate them and scan further from that point on. This way you can
scan in a single pass if the scanning process calls you back when it
finds a transaction and allows you to change the set of addresses on the
fly.
Jochen
📝 Original message:On 24.08.2016 16:18, Jonas Schnelli via bitcoin-dev wrote:
>
> Another thing that I think could be a BIP misdesign:
>
> BIP44 Gap Limits
> From the BIP:
>
> ----------
> "Address gap limit is currently set to 20. If the software hits 20
> unused addresses in a row, it expects there are no used addresses beyond
> this point and stops searching the address chain."
> ----------
>
> * Does that mean, we do a transaction rescan back to the genesis block
> for every 20 addresses?
As I understand it, you can scan sequentially starting with the genesis
block (or with a block at around the time when BIP44 was written). Then
if you find a new transaction, which requires to generate new addresses,
you generate them and scan further from that point on. This way you can
scan in a single pass if the scanning process calls you back when it
finds a transaction and allows you to change the set of addresses on the
fly.
Jochen