public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BloomFilter issue with segwit addresses
Date: Sun, 15 Apr 2018 20:37:45 +0200	[thread overview]
Message-ID: <pb061m$lj1$1@blaine.gmane.org> (raw)
In-Reply-To: <CALxbBHV=xpzu8iL-S=EKBc39QWvAiicVixM_j3Ve1TH+sngPoQ@mail.gmail.com>

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 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, so this might be a non-issue.
> 
> On Sat, Apr 14, 2018, 00:17 Jim Posen via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org
> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> 
>     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
>     <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> 
>         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 reject) a feature.
>         Someone needs to come up with a proposal (pull request).
> 
>         Maybe an extension for BIP37 would make sense (*meh*).
>         Just inserting the witness data into the bloom filter seems to
>         be an easy solution (CBloomFilter::IsRelevantAndUpdate())
> 
>         /jonas
> 
>         _______________________________________________
>         bitcoin-dev mailing list
>         bitcoin-dev@lists.linuxfoundation.org
>         <mailto:bitcoin-dev@lists.linuxfoundation.org>
>         https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 
> 
>     _______________________________________________
>     bitcoin-dev mailing list
>     bitcoin-dev@lists.linuxfoundation.org
>     <mailto:bitcoin-dev@lists.linuxfoundation.org>
>     https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 
> 
> 
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 




  parent reply	other threads:[~2018-04-15 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 15:32 [bitcoin-dev] BloomFilter issue with segwit addresses Andreas Schildbach
2018-04-13 19:12 ` Jonas Schnelli
2018-04-13 22:15   ` Jim Posen
2018-04-14 16:14     ` Christian Decker
2018-04-14 19:46       ` Jim Posen
2018-04-15 18:37       ` Andreas Schildbach [this message]
2018-04-13 22:52 ` Luke Dashjr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pb061m$lj1$1@blaine.gmane.org' \
    --to=andreas@schildbach.de \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox