Yes, I guess the quicker filter exhaustion must be the reason why
bitcoinj doesn't make use of outpoints in filters for standard
transactions. I'll look into if I can change that.
On 04/14/2018 06:14 PM, Christian Decker via bitcoin-dev wrote:
> Note that this would compound the privacy leak that
To Christian's point about privacy, I'll take this opportunity to
shamelessly review beg on https://github.com/bitcoin/bitcoin/pull/12254,
the PR for BIP 158 implementation (but not 157).
On Sat, Apr 14, 2018 at 9:14 AM, Christian Decker <
decker.christ...@gmail.com> wrote:
> Note that this would
Note that this would compound the privacy leak that Jonas Nick used to
identify address clusters via the bloom filters in one of his publications.
By reducing the false positives when matching you can get very detailed
clusters. Then again we know that bloom filters aren't good for privacy
anyway,
As I understand it, the plan is to deprecated and remove BIP37 entirely once
BIP158 is implemented and deployed.
In the meantime, Bitcoin Knots supports the MSG_FILTERED_WITNESS_BLOCK
extension to download witness data. (Note that light clients currently have no
way to verify the witness data i
Why not add the outpoints owned by the wallet to the filter and watch for
those instead of elements in the input script or witness data?
On Fri, Apr 13, 2018 at 12:12 PM, Jonas Schnelli via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi Andreas
>
> Thanks for bringing this up an
Hi Andreas
Thanks for bringing this up and this seems indeed to be suboptimal.
> I wonder if Bitcoin Core would be willing to extend the BIP37 matching
> rules such that data elements in the witness are also matched against?
Bitcoin Core is not an identity that can be „willing to extend“ (or rej
Anton, a developer on the bitcoinj maiing list, recently made me aware
[1] of a compatibility issue between segwit and BIP37 (Bloom Filtering).
The issue affects only P2WPKH and the special case of transactions
without change outputs (such as when emptying a wallet). In this case,
neither inputs n