Luke Dashjr [ARCHIVE] on Nostr: 📅 Original date posted:2019-07-27 📝 Original message:On Tuesday 23 July 2019 ...
📅 Original date posted:2019-07-27
📝 Original message:On Tuesday 23 July 2019 14:47:18 Andreas Schildbach via bitcoin-dev wrote:
> 3) Afaik, it enforces/encourages address re-use. This stems from the
> fact that the server decides on the filter and in particular on the
> false positive rate. On wallets with many addresses, a hardcoded filter
> will be too blurry and thus each block will be matched. So wallets that
> follow the "one address per incoming payment" pattern (e.g. HD wallets)
> at some point will be forced to wrap their key chains back to the
> beginning. If I'm wrong on this one please let me know.
BTW, you are indeed wrong on this. You don't need to match every single
address the wallet has ever used, only outstanding addresses that haven't
been paid. ;)
Luke
📝 Original message:On Tuesday 23 July 2019 14:47:18 Andreas Schildbach via bitcoin-dev wrote:
> 3) Afaik, it enforces/encourages address re-use. This stems from the
> fact that the server decides on the filter and in particular on the
> false positive rate. On wallets with many addresses, a hardcoded filter
> will be too blurry and thus each block will be matched. So wallets that
> follow the "one address per incoming payment" pattern (e.g. HD wallets)
> at some point will be forced to wrap their key chains back to the
> beginning. If I'm wrong on this one please let me know.
BTW, you are indeed wrong on this. You don't need to match every single
address the wallet has ever used, only outstanding addresses that haven't
been paid. ;)
Luke