From: Peter Todd <pete@petertodd•org>
To: Matt Corallo <lf-lists@mattcorallo•com>,
bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP
Date: Thu, 20 Aug 2015 22:42:19 -0700 [thread overview]
Message-ID: <20150821054219.GB18176@muck> (raw)
In-Reply-To: <20150821053819.GA18176@muck>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
On Thu, Aug 20, 2015 at 10:38:19PM -0700, Peter Todd via bitcoin-dev wrote:
> > Motivation
> > ==========
> >
> > BIP 37 did not specify a service bit for the bloom filter service, thus
> > implicitly assuming that all nodes that serve peers data support it.
> > However, the connection filtering algorithm proposed in BIP 37, and
> > implemented in several clients today, has been shown to provide little
> > to no privacy, as well as being a large DoS risk on some nodes. Thus,
> > allowing node operators to disable connection bloom filtering is a
> > much-needed feature.
>
> I'd reference that paper on bloom filters re: the "little to no privacy"
> issue. There's also a post in the bitcoinj mailing list somewhere IIRC
> talking about the default settings, and how they don't provide any
> privacy.
Oh, and we should also point out that Bloom filters have scaling issues,
as each application of the filter has to scan the whole blockchain -
with future blocksize increases these issues increase, in some proposals
quite dramatically. The underlying idea also conflicts with some
proposals to "shard" the blockchain, again suggesting that we need a bit
to handle future upgrades to more scalable designs.
--
'peter'[:-1]@petertodd.org
00000000000000000402fe6fb9ad613c93e12bddfc6ec02a2bd92f002050594d
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-08-21 5:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 4:46 Matt Corallo
2015-08-21 5:38 ` Peter Todd
2015-08-21 5:42 ` Peter Todd [this message]
2015-08-21 17:55 ` Matt Corallo
2015-08-21 22:06 ` Peter Todd
2015-08-22 1:08 ` Matt Corallo
2015-08-22 1:48 ` Peter Todd
2015-08-24 15:19 ` Tom Harding
2015-08-24 17:39 ` Matt Corallo
2015-08-22 1:08 ` Matt Corallo
2015-08-21 5:48 ` Jeff Garzik
2015-08-21 5:55 ` Peter Todd
2015-08-21 6:01 ` Jeff Garzik
2015-08-21 6:07 ` Peter Todd
2015-08-21 22:15 ` Chris Pacia
2015-08-21 22:25 ` Peter Todd
2015-08-21 23:08 ` Tom Harding
2015-08-24 15:21 ` Mike Hearn
2015-08-21 8:31 ` Andreas Schildbach
2015-08-21 17:53 ` Matt Corallo
2015-08-24 15:29 ` Wladimir J. van der Laan
2015-08-24 17:37 ` Matt Corallo
2015-08-24 17:41 ` Wladimir J. van der Laan
2015-08-24 17:58 ` Eric Lombrozo
2015-08-24 18:00 ` Peter Todd
2015-08-24 18:07 ` Matt Corallo
2015-08-24 18:15 ` Eric Lombrozo
2015-08-24 18:28 ` Matt Corallo
2015-08-24 18:30 ` Wladimir J. van der Laan
2015-08-24 18:33 ` Eric Lombrozo
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=20150821054219.GB18176@muck \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lf-lists@mattcorallo$(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