One more proposal:
* When sending filtered blocks, also send the witnesses (if any).
On 23/04/2019 13.43, Andreas Schildbach wrote:
> Since client-side filtering (BIP157/158) isn't really an option for
> light wallets, I'm thinking about how to improve server-side connection
> filtering (BIP37
1. Lack of support for unconfirmed tx. This alone degrades usage to an
optional "more privacy, but much slower" setting. I doubt that the
typical light wallet user cares much about privacy, but I can assert
users _extremely_ care about speed.
2. It doesn't scale, at least not unless multiple
It's great to see progress in this area.
Why client-side filtering is not an option for light wallets? Because
of lack of support for unconfirmed tx? Any other problem on top of
that one?
Adding here some related links:
https://groups.google.com/forum/#!msg/bitcoinj/Ys13qkTwcNg/9qxnhwnkeoIJ
Since client-side filtering (BIP157/158) isn't really an option for
light wallets, I'm thinking about how to improve server-side connection
filtering (BIP37 aka "bloom filters").
I propose the following changes to BIP37 (via a new BIP of course):
---
* A new matching rule
For each tx, each
