From: bitcoin-list@bluematt.me
To: Jeff Garzik <jgarzik@bitpay.com>,Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Combining bloom filters?
Date: Sat, 17 Aug 2013 10:03:41 -0400 [thread overview]
Message-ID: <19192d40-656d-4901-b9e0-165b43420b7d@email.android.com> (raw)
In-Reply-To: <CAJHLa0PfHa9Xinv0rdGUK8PRxR5NMC6h2an2ZGgCaTi_DpFrfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
Under some conditions, yes. The filters must have the same parameters (tweak, size, hash count). Bitcoinj implements this in its BloomFilter class.
Matt
Jeff Garzik <jgarzik@bitpay.com> wrote:
>Consider wallet A builds bloom filter A' and wallet B builds bloom
>filter B'. Can A' and B' be or'd together to form a single bloom
>filter C' ?
>
>--
>Jeff Garzik
>Senior Software Engineer and open source evangelist
>BitPay, Inc. https://bitpay.com/
>
>------------------------------------------------------------------------------
>Get 100% visibility into Java/.NET code with AppDynamics Lite!
>It's a free troubleshooting tool designed for production.
>Get down to code-level detail for bottlenecks, with <2% overhead.
>Download for free and get started troubleshooting in minutes.
>http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 616 bytes --]
next prev parent reply other threads:[~2013-08-17 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 14:00 [Bitcoin-development] Combining bloom filters? Jeff Garzik
2013-08-17 14:03 ` bitcoin-list [this message]
2013-08-17 14:15 ` Pieter Wuille
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=19192d40-656d-4901-b9e0-165b43420b7d@email.android.com \
--to=bitcoin-list@bluematt.me \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@bitpay.com \
--cc=mike@plan99.net \
/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