From: Peter Todd <pete@petertodd•org>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_BLOOM BIP
Date: Sun, 18 Aug 2013 19:11:09 -0400 [thread overview]
Message-ID: <20130818231109.GB23974@savin> (raw)
In-Reply-To: <CABsx9T2Jz1LUvKP38pMRGt6Vp5USzCUQL_F-pqsMsVygVzhiiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Mon, Aug 19, 2013 at 08:22:10AM +1000, Gavin Andresen wrote:
> Mike pointed out exactly the reason I oppose a NODE_BLOOM service bit: I
> also think it is a bad idea to start making various bits and pieces of the
> protocol optional.
> It is bad for privacy (easier to fingerprint nodes) and bad for
> decentralization (fewer nodes support your required feature set). And every
> bit you add can give you an exponential number of combinations your QA team
> should test.
Mike's and others have been talking about persistent node-specific
identifiers, and after all at this level there are IP addresses;
fingerprinting nodes is trivial.
> I'd say the same thing about NODE_TRANSACTION ("I don't know about blocks,
> have and NODE_BLOCK bits.
We need options so peopl can contribute to relaying and the health of
the network - these edge cases are going to be tested anyway by people
like me deciding to disable bloom filtering.
--
'peter'[:-1]@petertodd.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-08-18 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 2:59 Peter Todd
2013-08-18 22:00 ` Mike Hearn
2013-08-18 22:22 ` Gavin Andresen
2013-08-18 23:11 ` Peter Todd [this message]
2013-08-18 22:59 ` Peter Todd
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=20130818231109.GB23974@savin \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(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