From: Gavin Andresen <gavinandresen@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_BLOOM BIP
Date: Mon, 19 Aug 2013 08:22:10 +1000 [thread overview]
Message-ID: <CABsx9T2Jz1LUvKP38pMRGt6Vp5USzCUQL_F-pqsMsVygVzhiiQ@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2jONtRJ6oF1YqKJB9nm1HcMkfz_yzeNshEWqD-5fdNiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
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.
I'd say the same thing about NODE_TRANSACTION ("I don't know about blocks,
have and NODE_BLOCK bits.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 667 bytes --]
next prev parent reply other threads:[~2013-08-18 22:22 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 [this message]
2013-08-18 23:11 ` Peter Todd
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=CABsx9T2Jz1LUvKP38pMRGt6Vp5USzCUQL_F-pqsMsVygVzhiiQ@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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