From: Pieter Wuille <pieter.wuille@gmail•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Combining bloom filters?
Date: Sat, 17 Aug 2013 16:15:31 +0200 [thread overview]
Message-ID: <CAPg+sBhHmXx_qV7i-9rSBHsV7U7AET7b+FXecRuROMF=R2UJhA@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0PfHa9Xinv0rdGUK8PRxR5NMC6h2an2ZGgCaTi_DpFrfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
If both constructed bloom filters use the same seed and the same number of
hash functions, yes. Assuming the input filters were optimal for a given FP
rate, the resulting filter will be worse.
--
Pieter
On 17 Aug 2013 16:01, "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: 1835 bytes --]
prev parent reply other threads:[~2013-08-17 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 14:00 Jeff Garzik
2013-08-17 14:03 ` bitcoin-list
2013-08-17 14:15 ` Pieter Wuille [this message]
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='CAPg+sBhHmXx_qV7i-9rSBHsV7U7AET7b+FXecRuROMF=R2UJhA@mail.gmail.com' \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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